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

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


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

health-plan-webview-phone
perf-go-webview-phone

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

=== 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:native_heap:proportional_resident_size_avg/browse_news/browse_news_cricbuzz
  Change       : 0.98% | 35322248.7619 -> 34976380.5714

Revision                       Result                  N
android-chrome@513a55000f      35322249 +- 578356      21      good
android-chrome@5c668f813d      34976381 +- 532121      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.cricbuzz 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/8940101080989175360


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please 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:native_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science


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.m.youtube.com.results.q.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/8940088372843365744


For feedback, file a bug with component Speed>Bisection