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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Compile:duration_avg/browse_tools/browse_tools_maps

Revision             Result                  N
chromium@507871      447.93 +- 20.2588       21      good
chromium@507922      447.861 +- 22.1546      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.tools.maps 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/8964954581216307056


For feedback, file a bug with component Speed>Bisection

not reproducible