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

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


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

perf-go-webview-phone

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 0.63% | 4336814.47619 -> 4363965.33333

Revision                       Result                 N
android-chrome@3046567591      4336814 +- 150303      21      good
android-chrome@d53b7a6787      4363965 +- 171859      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=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/8941494022581719472


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 3.41% | 4237468.7619 -> 4382113.52381

Revision                       Result                  N
android-chrome@5b7a7e3ac6      4237469 +- 62796.8      21      good
android-chrome@fd216597cf      4295998 +- 153706       21      unknown
android-chrome@22df6667c5      4382114 +- 156159       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=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/8941216764235419216


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 1.81% | 4232264.7619 -> 4309071.04762

Revision                       Result                  N
android-chrome@e84fac5ecd      4232265 +- 32503.9      21      good
android-chrome@6b0818a7a5      4309071 +- 173544       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=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/8941131021702996560


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 0.29% | 4315547.61905 -> 4303119.61905

Revision                       Result                 N
android-chrome@3046567591      4315548 +- 159354      21      good
android-chrome@d53b7a6787      4303120 +- 159773      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=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/8940857846212573648


For feedback, file a bug with component Speed>Bisection

Bisect can't find anything in the noise - the other benchmarks under the same category look fine, nothing really actionable here.