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

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


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

perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/background/after_https_m_facebook_com_rihanna
  Change       : 1.21% | 23191552.0 -> 23582037.3333

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/3a3f199d08ab6ec49ff765417936c945c5fae72e..2b81be59661f7014eab10658327801f80b5b1ebf


Revision                                       Result                   N
android-chrome@f9e3d7603e                      23191552 +- 143114       6        good
android-chrome@fbe9ad968a                      23137849 +- 184325       9        good
android-chrome@fbe9ad968a,chromium@555768      23264695 +- 226653       14       good
android-chrome@fbe9ad968a,chromium@555769      ---                      ---      build failure
android-chrome@fbe9ad968a,chromium@555770      23672149 +- 162311       6        bad
android-chrome@fbe9ad968a,chromium@555771      23757483 +- 191146       6        bad
android-chrome@fbe9ad968a,chromium@555774      23755435 +- 92669.8      6        bad
android-chrome@fbe9ad968a,chromium@555779      23541760 +- 149192       6        bad
android-chrome@9af30a5037                      23582037 +- 193110       9        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=https.m.facebook.com.rihanna 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/8946994174272805696


For feedback, file a bug with component Speed>Bisection

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.