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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/http___ie.microsoft.com_testdrive_Performance_FishIETank_Default.html

Revision             Result                  N
chromium@507551      18.8688 +- 30.1801      21      good
chromium@507597      17.7048 +- 2.94554      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=http...ie.microsoft.com.testdrive.Performance.FishIETank.Default.html smoothness.tough_canvas_cases

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

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


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.