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

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


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

android-nexus5X
chromium-rel-win7-gpu-nvidia
linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-start_sum/browse_social/browse_social_facebook_infinite_scroll

Revision             Result                    N
chromium@485714      0.824429 +- 0.786829      21      good
chromium@485896      0.94519 +- 0.968921       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.facebook.infinite.scroll 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/8973651538448496096


For feedback, file a bug with component Speed>Bisection

We didn't have data for a long time and the alerts started happening on the first spike that is within noise.