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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_social/browse_social_facebook_infinite_scroll

Revision             Result                  N
chromium@489964      276.623 +- 361.484      21      good
chromium@490022      272.628 +- 391.603      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook.infinite.scroll 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/8972264937445723008


For feedback, file a bug with component Speed>Bisection

Not reproducible.