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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/video.html?src_tulip2.mp4

Revision             Result              N
chromium@512898      5619712 +- 0.0      21      good
chromium@513282      5619712 +- 0.0      21      bad

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.tulip2.mp4 media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Bisect isn't working right?