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

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


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

chromium-rel-win8-dual

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

=== 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_canvas_toBlob.html

Revision             Result                   N
chromium@493983      21.2016 +- 0.785009      21      good
chromium@493985      21.5824 +- 4.75405       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.canvas.toBlob.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/8970000027355844064


For feedback, file a bug with component Speed>Bisection

This just happened on one case and one bot and bisect cannot repro.