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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_social/browse_social_twitter

Revision             Result                  N
chromium@516127      47.2133 +- 36.0187      21      good
chromium@516223      43.848 +- 42.6591       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.social.twitter 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/8962309835383293072


For feedback, file a bug with component Speed>Bisection

Closing as not reproducible.