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

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


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

chromium-rel-win7-dual

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

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

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

Revision             Result                 N
chromium@459636      12.034 +- 16.8676      21      good
chromium@459651      11.631 +- 4.94339      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --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/8983804801423234944

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


| 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!

Bisect bot cannot reproduce the regression, which seems to come from revert of previous improvement.