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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Total:duration_avg/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                  N
chromium@509758      13132.3 +- 680.771      21      good
chromium@509795      13171.1 +- 560.459      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.media.flickr.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/8964954644143701760


For feedback, file a bug with component Speed>Bisection

not reproducible