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

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


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

health-plan-clankium-low-end-phone
perf-go-phone-1024
perf-go-phone-512
perf-go-webview-phone

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

=== 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: 5c054be784d9ad459acca06522482cd32092bce1
  bad_revision : 44010e122e561daf7d969f2d8d3c256775129d2d

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:system_memory:private_footprint_size_avg/browse_news/browse_news_reddit
  Change       : 1.29% | 59051576.8889 -> 59811612.4444

Revision                                       Result                  N
android-chrome@99b6fd7dae                      59051577 +- 325429      9       good
android-chrome@6d62ea7763                      58426027 +- 268260      6       good
android-chrome@e5eafcf94f                      58770318 +- 169722      9       good
android-chrome@e5eafcf94f,chromium@575869      58749513 +- 359092      14      good
android-chrome@e5eafcf94f,chromium@575874      59419989 +- 415920      6       bad
android-chrome@e5eafcf94f,chromium@575882      59053787 +- 131855      14      bad
android-chrome@e5eafcf94f,chromium@575894      59120884 +- 353278      21      bad
android-chrome@74662f91c8                      59137170 +- 389460      14      bad
android-chrome@1032e70048                      59928576 +- 451683      6       bad
android-chrome@478583399d                      59901269 +- 317007      6       bad
android-chrome@029430f630                      59811612 +- 495456      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=browse.news.reddit 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/8940201543621311104


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please 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:system_memory:private_footprint_size_avg/browse_news/browse_news_reddit


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.news.reddit 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/8940104158151047536


For feedback, file a bug with component Speed>Bisection

Simon, any idea what's going on here?