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

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


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

health-plan-webview-phone

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

=== 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: d5c7eab4bf9e9c72815f5eebb7a10936228786ef
  bad_revision : dd0f00b919e8fd932c2b63871463ffbc17194d1d

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/load_chrome/load_chrome_blank
  Change       : 2.00% | 10786529.7143 -> 10957854.6667

Revision                                       Result                   N
android-chrome@a1d466a294                      10786530 +- 69687.1      14      good
android-chrome@a1d466a294,chromium@559889      10840875 +- 71255.3      14      good
android-chrome@a1d466a294,chromium@559892      10809375 +- 56928.8      9       good
android-chrome@a1d466a294,chromium@559894      10971679 +- 85758.2      6       bad
android-chrome@a1d466a294,chromium@559898      10930255 +- 78094.5      14      bad
android-chrome@0cf60053f7                      10957855 +- 78298.6      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=load.chrome.blank 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/8945179970997939440


For feedback, file a bug with component Speed>Bisection