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

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


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

health-plan-webview-phone

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

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

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_media/browse_media_facebook_photos
  Change       : 0.07% | 90470711.2381 -> 90532200.0

Revision                       Result                  N
android-chrome@2583170ec8      90470711 +- 618676      21      good
android-chrome@6fa426c2e3      90532200 +- 848477      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.media.facebook.photos 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/8943706264433095440


For feedback, file a bug with component Speed>Bisection