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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/canvas_90000_pixels_per_second

Revision             Result                  N
chromium@511327      6.34477 +- 2.54867      21      good
chromium@511368      6.23455 +- 1.86913      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=canvas.90000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Just a single device/test case and bisect can't repro.