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

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


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

health-plan-clankium-phone

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Troy Hildebrandt
  Commit : 70713a2e5e13826d9d1fa4356277b4369f6d34bd
  Date   : Tue May 08 18:39:45 2018
  Subject: Revert "Reland "Update gcore to v16.1""

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_tools/load_tools_docs
  Change       : 1.18% | 48870230.6667 -> 49445036.0

Revision                       Result                  N
android-chrome@8f25dd139d      48870231 +- 176031      6      good
android-chrome@b425a64a09      48912556 +- 239562      6      good
android-chrome@70713a2e5e      49445036 +- 140815      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.tools.docs 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/8946531554915047232


For feedback, file a bug with component Speed>Bisection