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

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


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

health-plan-clankium-phone

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/load_chrome/load_chrome_blank
  Change       : 2.23% | 39958700.0 -> 40850262.6667

Suspected Commit Range
  13 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4f6f43dc5122f5404a9b7b4d696251eada4d4627..9d129ed85feafc7fb807d741f962edb05047acff


Revision                                       Result                   N
android-chrome@fbe9ad968a                      39958700 +- 153297       6        good
android-chrome@fbe9ad968a,chromium@555759      39915692 +- 125981       6        good
android-chrome@fbe9ad968a,chromium@555761      39769601 +- 154255       6        good
android-chrome@fbe9ad968a,chromium@555762      ---                      ---      build failure
---                                            ---                      ---      too many build failures to list
android-chrome@fbe9ad968a,chromium@555773      ---                      ---      build failure
android-chrome@fbe9ad968a,chromium@555774      40771073 +- 93955.4      6        bad
android-chrome@9af30a5037                      40850263 +- 71904.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=load.chrome.blank 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/8947094903366531024


For feedback, file a bug with component Speed>Bisection

Regression has recovered