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

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


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

perf-go-webview-phone

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

=== 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_chrome:gpu:effective_size_avg/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 0.00% | 7125674.66667 -> 7125674.66667

Revision                       Result                  N
android-chrome@8062d9e01c      7125675 +- 1601726      21      good
android-chrome@2a3c2c255c      7125675 +- 1601726      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.social.pinterest.infinite.scroll 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/8942356227240229952


For feedback, file a bug with component Speed>Bisection