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

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


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

chromium-rel-win7-dual
chromium-rel-win8-dual
win-high-dpi

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

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

Revision             Result                  N
chromium@490325      54.1095 +- 2.28423      21      good
chromium@490447      54.4284 +- 2.82846      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.canvas.lines.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/8972368123588145376


For feedback, file a bug with component Speed>Bisection

Clear regressions came back down, bisect failed to repro.