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

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


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

android-nexus5
android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_tech/browse_tech_discourse_infinite_scroll

Revision             Result                 N
chromium@488886      39.743 +- 58.9277      21      good
chromium@488899      36.176 +- 55.3314      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.tech.discourse.infinite.scroll v8.runtimestats.browsing_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972178154849759520


For feedback, file a bug with component Speed>Bisection

Not reproducible. Graphs have recovered.