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

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


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
health-plan-webview-phone
perf-go-phone-1024
perf-go-phone-512
perf-go-webview-phone

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

=== 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: 4a9d09e563df548cea6a3ad93a7c4f293a8f7633
  bad_revision : 5b7648dcf47af986f69d54b9a6011f51a8092020

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


Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 35.18% | 865916.0 -> 1170560.0

Revision                                       Result              N
android-chrome@99b6fd7dae                      865916 +- 0.0       6      good
android-chrome@6d62ea7763                      865796 +- 0.0       6      good
android-chrome@e5eafcf94f                      865796 +- 0.0       6      good
android-chrome@74662f91c8                      865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575926      865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575929      865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575931      1170560 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575935      1170560 +- 0.0      6      bad
android-chrome@1032e70048                      1170560 +- 0.0      6      bad
android-chrome@478583399d                      1170560 +- 0.0      6      bad
android-chrome@029430f630                      1170560 +- 0.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=browse.chrome.newtab 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/8940539914405214304


For feedback, file a bug with component Speed>Bisection