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

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


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

perf-go-phone-1024

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

=== 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: 3043a5ceb86386b72ae45d73e98b2502106d66e1
  bad_revision : b7716f40b7eca0d4c54535f78a2fe05de1f66575

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_os:system_memory:java_heap:proportional_resident_size_avg/load_search/load_search_taobao
  Change       : 47.03% | 2509482.66667 -> 3689813.33333

Revision                                       Result                  N
android-chrome@b50c37440c                      2509483 +- 176398       6      good
android-chrome@b50c37440c,chromium@560639      2491392 +- 161171       6      good
android-chrome@b50c37440c,chromium@560648      2506411 +- 183497       6      good
android-chrome@b50c37440c,chromium@560652      2443605 +- 203310       6      good
android-chrome@b50c37440c,chromium@560656      3663872 +- 82684.4      6      bad
android-chrome@b50c37440c,chromium@560690      3751253 +- 51251.9      6      bad
android-chrome@3e4ba1f0ce                      3678891 +- 54734.4      6      bad
android-chrome@5c07f907f2                      3689813 +- 42991.7      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=load.search.taobao 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/8945193057379556560


For feedback, file a bug with component Speed>Bisection