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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-finalize_max/browse_media/browse_media_pinterest

Revision             Result                   N
chromium@492245      0.661476 +- 3.62315      21      good
chromium@492248      0.650905 +- 3.6543       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.pinterest 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/8971563596468564880


For feedback, file a bug with component Speed>Bisection

No repro, regression disappeared.