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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/tough_canvas_cases_rendering_throughput_put_get_image_data.html

Revision             Result                  N
chromium@489984      19.5504 +- 1.07883      21      good
chromium@490053      19.7003 +- 0.72963      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=tough.canvas.cases.rendering.throughput.put.get.image.data.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/8972297794768718320


For feedback, file a bug with component Speed>Bisection

Bisect didn't reproduce