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

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


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
perf-go-phone-512
perf-monochrome-o-phone

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

=== 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 : 21289d5be9936171c5ed5d8a0c8e7ed361f971f1

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


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 44.30% | 688892.0 -> 994104.0

Revision                                       Result             N
android-chrome@74662f91c8                      688892 +- 0.0      6      good
android-chrome@74662f91c8,chromium@575926      688892 +- 0.0      6      good
android-chrome@74662f91c8,chromium@575929      688892 +- 0.0      6      good
android-chrome@74662f91c8,chromium@575930      994104 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575931      994104 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575935      994104 +- 0.0      6      bad
android-chrome@1032e70048                      994104 +- 0.0      6      bad
android-chrome@4e67b217c5                      994104 +- 0.0      6      bad
android-chrome@bdf6ddc146                      994104 +- 0.0      6      bad
android-chrome@478583399d                      994104 +- 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/8940539973326748656


For feedback, file a bug with component Speed>Bisection