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

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


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

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

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

=== 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: 46898d23cdf5f209e6e40a1b8509682919efa4d5
  bad_revision : aceb7d670d0cca38d219cadfc529390c755c299c

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


Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_cnn
  Change       : 16.67% | 79795214.6667 -> 93098340.0

Revision                                       Result                   N
android-chrome@cd18451841                      79795215 +- 794782       6      good
android-chrome@cd18451841,chromium@565955      79727119 +- 646508       6      good
android-chrome@cd18451841,chromium@565961      79731044 +- 820286       6      good
android-chrome@cd18451841,chromium@565967      92977508 +- 1816351      6      bad
android-chrome@cd18451841,chromium@565991      92078777 +- 3521894      6      bad
android-chrome@cd18451841,chromium@566039      93611023 +- 5546040      6      bad
android-chrome@cd18451841,chromium@566135      93714788 +- 2681000      6      bad
android-chrome@cd18451841,chromium@566328      93854905 +- 2792198      6      bad
android-chrome@b1b15efc34                      93285391 +- 4414440      6      bad
android-chrome@9cd870ee9e                      93098340 +- 1554545      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn 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/8943756800630485808


For feedback, file a bug with component Speed>Bisection

Graphs recovered.