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

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


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

win-high-dpi

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

=== 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:gpu:effective_size_avg/video.html?src_tulip2.vp9.webm_background

Revision             Result                   N
chromium@508229      18492736 +- 3068.24      21      good
chromium@508324      18492811 +- 2830.49      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.vp9.webm.background media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Won't fix. Bisect failed and bug is stale.