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

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


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

win-high-dpi

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

=== 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       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:effective_size_avg


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 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/8970677031158708768


For feedback, file a bug with component Speed>Bisection

no bisect, closing as WontFix.