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

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


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

win-high-dpi

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

=== 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:malloc:effective_size_avg/video.html?src_tulip2.mp3_type_audio_seek

Revision             Result                  N
chromium@512682      13005660 +- 267526      21      good
chromium@512776      13010392 +- 225801      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.mp3.type.audio.seek media.desktop

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

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


For feedback, file a bug with component Speed>Bisection