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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_background_tbmv2
  Metric       : v8-gc-incremental-step_avg/v8-gc-incremental-step_avg

Revision             Result                  N
chromium@492969      0.776447 +- 0.1658      21      good
chromium@493150      0.92701 +- 1.19043      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 memory.long_running_idle_gmail_background_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

This came back down.