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

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


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

chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_hover_15000_pixels_per_second
  Change       : 1.15% | 0.414584992953 -> 0.41935270392

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/e04d39989fc56c1c959c34ccfe022c60605401af..b36cc32a9c6e39789189d9c4095ab01ad1e020be


Revision             Result                      N
chromium@506698      0.414585 +- 0.00852584      14       good
chromium@506719      0.415221 +- 0.0121165       14       good
chromium@506728      0.415246 +- 0.0147777       21       good
chromium@506734      0.417808 +- 0.038813        14       good
chromium@506735      ---                         ---      build failure
chromium@506736      0.418849 +- 0.014676        14       bad
chromium@506738      0.420146 +- 0.0211863       14       bad
chromium@506777      0.419353 +- 0.0180023       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=text.hover.15000.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/8965831462485413776


For feedback, file a bug with component Speed>Bisection

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