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

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


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

health-plan-webview-phone

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 09e987354f7113ab5ba670613d9f42271c76337d
  bad_revision : 99231f828e5b2855f9eedc09a9da968dd4c34bc7

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_chrome:java_heap:allocated_objects_size_avg/background_news/background_news_nytimes
  Change       : 27.07% | 16216261.3333 -> 20606002.6667

Revision                                       Result                   N
android-chrome@ca1c4e48aa                      16216261 +- 200.905      6      good
android-chrome@2158fc5105                      16216359 +- 68.71        6      good
android-chrome@2158fc5105,chromium@566949      16216741 +- 177.136      6      good
android-chrome@2158fc5105,chromium@566970      16211795 +- 12070.6      6      good
android-chrome@2158fc5105,chromium@566980      20107161 +- 565296       6      bad
android-chrome@2158fc5105,chromium@566991      19976416 +- 458497       6      bad
android-chrome@f6b5646c5d                      20370571 +- 626271       6      bad
android-chrome@adcd19c5ad                      20606003 +- 422264       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=background.news.nytimes 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/8943706213537809600


For feedback, file a bug with component Speed>Bisection