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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/canvas_40000_pixels_per_second

Revision             Result                  N
chromium@498509      13.3329 +- 7.21252      21      good
chromium@498638      13.116 +- 8.07621       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=canvas.40000.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/8969252931564055248


For feedback, file a bug with component Speed>Bisection

This has recovered.