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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgpLDv4wgM


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-total_max/browse_media/browse_media_youtube

Revision             Result                  N
chromium@452431      15.9208 +- 7.59731      21      good
chromium@452538      17.325 +- 14.4185       21      unknown
chromium@452644      17.722 +- 12.2613       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=browse.media.youtube v8.browsing_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8986140392399848576

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5233717435432960


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!