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

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


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

perf-go-phone-512

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

=== 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: a8d64498704c018f73ce83393b2b341503896838
  bad_revision : 3fea53a776c473cd95cd43bb772cf479cc3c924a

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_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_dropbox
  Change       : 4.33% | 9842100.85714 -> 10324551.1429

Revision                       Result                   N
android-chrome@2cf1e6b65f      9842101 +- 110946        14       good
android-chrome@694b6c8369      9784280 +- 132722        9        good
android-chrome@a8d6449870      9846327 +- 113131        9        good
android-chrome@85cd864311      ---                      ---      build failure
android-chrome@2f39384013      ---                      ---      build failure
android-chrome@cba92f7f8b      ---                      ---      build failure
android-chrome@481ba81ad9      ---                      ---      build failure
android-chrome@3fea53a776      10252741 +- 387307       9        bad
android-chrome@70a5c38d16      10069916 +- 960880       21       bad
android-chrome@6c616c3855      10324551 +- 72876.0      14       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.dropbox 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/8945182980478094160


For feedback, file a bug with component Speed>Bisection