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

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


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

chromium-rel-win7-dual

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

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

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


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : total:500ms_window:renderer_eqt:v8:gc:scavenger_max/total:500ms_window:renderer_eqt:v8:gc:scavenger_max


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8974107187186451120


For feedback, file a bug with component Speed>Bisection

some graphs have missing data, the others recovered.