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

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


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

health-plan-webview-phone

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

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

Please try rerunning the bisect.


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_tools/load_tools_docs
  Change       : 1.18% | 18882249.3333 -> 19104286.6667

Revision                       Result                   N
android-chrome@722d4fc088      18882249 +- 21786.6      6      good
android-chrome@4c136b3e1c      19104287 +- 100012       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.tools.docs 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/8945006184393743088


For feedback, file a bug with component Speed>Bisection

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

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

Please try rerunning the bisect.


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_tools/load_tools_docs
  Change       : 1.62% | 18844532.0 -> 19149172.0

Revision                       Result                   N
android-chrome@722d4fc088      18844532 +- 69056.6      6      good
android-chrome@4c136b3e1c      19149172 +- 117148       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.tools.docs 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/8944906709106031424


For feedback, file a bug with component Speed>Bisection

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

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

Please try rerunning the bisect.


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_tools/load_tools_docs
  Change       : 1.69% | 18891465.3333 -> 19211465.3333

Revision                       Result                   N
android-chrome@722d4fc088      18891465 +- 73937.2      6      good
android-chrome@4c136b3e1c      19211465 +- 101902       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.tools.docs 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/8943969079513781712


For feedback, file a bug with component Speed>Bisection

Simon, can you take a look at the bisect?

Hit the 24 hour limit, largely because it looks like chrome was broken in part of the range and the recipe can't find a working build before time is up. We likely won't be able to make much progress here until Pinpoint does clank.

+dtu to kick this off on clank once Pinpoint supports it.