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

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


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

perf-go-webview-phone

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

=== 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: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
  Change       : 1.15% | 38630741.3333 -> 39074669.7143

Revision                                       Result                  N
android-chrome@cf28be054f                      38630741 +- 392106      21      good
android-chrome@e5eafcf94f                      38554185 +- 288710      14      good
android-chrome@e5eafcf94f,chromium@575869      38928384 +- 325511      14      bad
android-chrome@74662f91c8                      39074670 +- 387615      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=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940541516275517312


For feedback, file a bug with component Speed>Bisection