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

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


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

health-plan-webview-low-end-phone
perf-go-webview-phone
perf-monochrome-n-phone

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

=== 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-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/background_media/background_media_imgur

Revision                                       Result              N
android-chrome@cd22f0f943                      0.0 +- 0.0          6      good
android-chrome@cd22f0f943,chromium@576157      0.0 +- 0.0          6      good
android-chrome@c0e3d62ff2                      1048576 +- 0.0      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.media.imgur 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/8940541165353599536


For feedback, file a bug with component Speed>Bisection