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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Evan Stade
  Commit : ad2949ac9cb3919d1f3866f10dd2e03cc1856e2a
  Date   : Fri Aug 11 17:44:17 2017
  Subject: Count a WebContents as "no longer waiting for response" after receiving

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/video.html?src_crowd1080.mp4
  Change       : 1.94% | 117353.666667 -> 119624.777778

Revision             Result                 N
chromium@493774      117354 +- 4045.73      9      good
chromium@493787      116789 +- 794.697      6      good
chromium@493788      117452 +- 1315.33      6      good
chromium@493789      119420 +- 1286.2       6      bad       <--
chromium@493790      119685 +- 1303.57      6      bad
chromium@493793      119691 +- 1125.93      6      bad
chromium@493799      119802 +- 1676.32      9      bad
chromium@493824      119679 +- 1025.98      9      bad
chromium@493874      119625 +- 2133.74      9      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.crowd1080.mp4 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/8970677439360250224


For feedback, file a bug with component Speed>Bisection