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

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


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

health-plan-webview-low-end-phone

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

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

Bisect Details
  Configuration: webview-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 0.99% | 15065088.0 -> 15214884.5714

Revision                       Result                   N
android-chrome@de28fbbddb      15065088 +- 1341809      21      good
android-chrome@d4545992c5      15214885 +- 1231160      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=browse.news.qq 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/8942005996578882080


For feedback, file a bug with component Speed>Bisection