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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max/total:500ms_window:renderer_eqt:v8:gc:latency-mark-compactor_max


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 v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection