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

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


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

chromium-rel-mac11
chromium-rel-mac12-mini-8gb
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_max/browse_tools/browse_tools_earth

Revision             Result                  N
chromium@514431      7.85456 +- 13.4516      18      good
chromium@514476      7.53571 +- 11.2517      17      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.tools.earth v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.