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

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


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

perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_docs
  Change       : 2.16% | 9612677.42857 -> 9405341.80952

Revision                       Result                  N
android-chrome@4c136b3e1c      9612677 +- 1302845      21      good
android-chrome@dd13b89214      9405342 +- 917303       21      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/8945192625479132816


For feedback, file a bug with component Speed>Bisection