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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : story:power_avg/video.html?src_crowd1080_vp9.webm


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=video.html.src.crowd1080.vp9.webm media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970677175571933968


For feedback, file a bug with component Speed>Bisection

Frank, Please follow up to clean up this bug.

Bisect didn't find a culprit, and now the regression is stale.