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

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


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

health-plan-clankium-low-end-phone
health-plan-clankium-phone
health-plan-webview-phone
perf-go-phone-1024

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: fe91e0bd6985093ced84dbada118ea56e312f92e
  bad_revision : 0b49d9f52a876f2272f72b3391b027f315a981d1

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/long_running_tools/long_running_tools_gmail-foreground
  Change       : 8.66% | 5628353.46405 -> 6115556.05882

Revision                                                     Result                  N
android-chrome@a03058257f                                    5628353 +- 80533.7      6      good
android-chrome@159f504c2c                                    5860579 +- 109299       6      good
android-chrome@df355fb4de                                    5820598 +- 69362.1      6      good
android-chrome@ff724a2dc4                                    5897977 +- 85736.5      6      good
android-chrome@ff724a2dc4,chromium@557527                    5828038 +- 160049       6      good
android-chrome@ff724a2dc4,chromium@557538                    5841014 +- 88942.4      6      good
android-chrome@ff724a2dc4,chromium@557538,v8@33157f3de7      5879328 +- 67853.7      6      good
android-chrome@ff724a2dc4,chromium@557538,v8@fe91e0bd69      5841840 +- 164447       6      good
android-chrome@ff724a2dc4,chromium@557538,v8@0b49d9f52a      6166369 +- 127768       6      bad
android-chrome@ff724a2dc4,chromium@557539                    6144315 +- 72250.4      6      bad
android-chrome@ff724a2dc4,chromium@557540                    6275879 +- 163573       6      bad
android-chrome@ff724a2dc4,chromium@557541                    6294653 +- 145124       6      bad
android-chrome@ff724a2dc4,chromium@557543                    6186369 +- 102973       6      bad
android-chrome@ff724a2dc4,chromium@557548                    6182134 +- 112367       6      bad
android-chrome@ff724a2dc4,chromium@557589                    6071761 +- 76496.5      9      bad
android-chrome@e65cccf457                                    6179878 +- 164815       6      bad
android-chrome@1bfcb4ee3d                                    6128474 +- 73054.5      6      bad
android-chrome@120ca38372                                    6115556 +- 104162       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection