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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-full-mark-compactor_avg/browse_media/browse_media_imgur

Revision             Result                  N
chromium@455037      74.8903 +- 8.68162      21      good
chromium@455056      74.5793 +- 10.1391      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.imgur v8.browsing_desktop

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

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


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

Regression recovered in the meantime.