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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_media/browse_media_imgur

Revision             Result                  N
chromium@517095      5981.13 +- 333.7        21      good
chromium@517142      5954.34 +- 245.685      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.imgur 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/8961778403171865680


For feedback, file a bug with component Speed>Bisection

not reproducible