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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

The bisect was able to narrow the range, you can try running with:
  good_revision: 358ed727fd6a9ecbf648c7e83b0ea2a65050134c
  bad_revision : 6a4bf41e0952e2b7793ab06940b10ec0e601c28b

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_hover_90000_pixels_per_second
  Change       : 402.10% | 1.96690571805 -> 9.8758131047

Revision             Result                   N
chromium@515932      1.96691 +- 0.392285      6      good
chromium@515955      2.05643 +- 0.439939      6      good
chromium@515966      1.92963 +- 0.367435      6      good
chromium@515968      9.99427 +- 0.278314      6      bad
chromium@515969      9.86929 +- 0.459793      6      bad
chromium@515972      9.8724 +- 0.517082       6      bad
chromium@515977      9.87581 +- 0.47007       6      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=text.hover.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/8962923160365709600


For feedback, file a bug with component Speed>Bisection

Looks like it's https://chromium.googlesource.com/chromium/src/+/cbeb064ce8a422528be2e2e6eca1942333628f01.

This is probably WontFix?

Yup. This makes sense since we're now scrolling slow enough (previously we'd get to the page almost instantly) to actually raster more parts of the page so I'd expect the raster thread to be busier.