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

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


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

perf-go-phone-1024

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

=== 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: 734de4c06e9357f1adffc0e524eeb4aaa676a628
  bad_revision : 6394ae6a5563fbb0bc386c3fc08c4cac65d7ecd8

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:malloc:effective_size_avg/background_tools/background_tools_gmail
  Change       : 2.04% | 16821340.6429 -> 17164592.5556

Revision                                       Result                   N
android-chrome@df6203e427                      16821341 +- 372692       14      good
android-chrome@a03058257f                      16300055 +- 278732       6       good
android-chrome@a03058257f,chromium@557108      16514082 +- 350079       9       good
android-chrome@a03058257f,chromium@557153      16377993 +- 15549.7      6       good
android-chrome@a03058257f,chromium@557164      16231084 +- 364087       6       good
android-chrome@a03058257f,chromium@557170      17123382 +- 23605.7      6       bad
android-chrome@a03058257f,chromium@557175      17129074 +- 24812.7      6       bad
android-chrome@a03058257f,chromium@557197      17280320 +- 24809.0      6       bad
android-chrome@6bb0def17f                      17162832 +- 227599       6       bad
android-chrome@50de738d9d                      17279374 +- 29799.4      6       bad
android-chrome@6e3e120710                      17255624 +- 20774.5      6       bad
android-chrome@f6c939c39e                      17258344 +- 24304.2      6       bad
android-chrome@be940e8741                      17285136 +- 18064.4      6       bad
android-chrome@e65cccf457                      17280670 +- 34835.8      6       bad
android-chrome@4426288b2b                      17164593 +- 268754       9       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=background.tools.gmail 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/8945111177299463376


For feedback, file a bug with component Speed>Bisection