All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=749330

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=1d16a4b85731677ed9d75ce960d8b043b4c34b73e181c5347ffcb5be3c446e94


Bot(s) for this bug's original alert(s):

android-one
android-webview-nexus5X
android-webview-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972962156029600544

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/IE Chalkboard

Revision             Result                  N
chromium@489153      104.982 +- 38.3621      21      good
chromium@489240      107.736 +- 35.6145      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=IE.Chalkboard smoothness.gpu_rasterization.tough_path_rendering_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972962156029600544


For feedback, file a bug with component Speed>Bisection

Measurements seem to be flaky. They have recovered (and are rather volatile).