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

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


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

health-plan-clankium-low-end-phone
health-plan-clankium-phone
health-plan-webview-low-end-phone

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 4263cfccd50ca0fe62d61caa5a67fb71c6e3a61e
  bad_revision : bc61b43fe11e77696ba2717eea5028f5c31ceb70

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:allocated_objects_size_avg/long_running_tools/long_running_tools_gmail-foreground
  Change       : 4.72% | 4991427.44444 -> 5226779.51634

Revision                                       Result                  N
android-chrome@a03058257f                      4991427 +- 78368.5      6      good
android-chrome@159f504c2c                      4812853 +- 43758.5      6      good
android-chrome@df355fb4de                      4781335 +- 64373.4      6      good
android-chrome@ff724a2dc4                      4775347 +- 49582.1      6      good
android-chrome@ff724a2dc4,chromium@557527      4804044 +- 76293.0      6      good
android-chrome@ff724a2dc4,chromium@557538      4768791 +- 81859.9      6      good
android-chrome@ff724a2dc4,chromium@557541      5216561 +- 49241.0      6      bad
android-chrome@ff724a2dc4,chromium@557543      5245528 +- 59309.0      6      bad
android-chrome@ff724a2dc4,chromium@557548      5213775 +- 54017.1      6      bad
android-chrome@ff724a2dc4,chromium@557589      5280094 +- 37226.4      6      bad
android-chrome@e65cccf457                      5180096 +- 18381.2      6      bad
android-chrome@1bfcb4ee3d                      5226902 +- 77287.1      6      bad
android-chrome@120ca38372                      5226780 +- 68297.0      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/8946561153108122608


For feedback, file a bug with component Speed>Bisection