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

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


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

chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-high-dpi

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:full-mark-compactor_max


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 v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection