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

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


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

perf-go-webview-phone

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

=== 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    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_search/load_search_taobao
  Change       : 2.04% | 18050172.3333 -> 18419120.5

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ff0961b08c823f09670a47084d32420191f9cc81..976fc1e074a07d78fc4ccb3ab2a9fbd20fd9ce69


Revision                                       Result                   N
android-chrome@7efa2ba1f1                      18050172 +- 112531       6        good
android-chrome@972eebff76                      18108830 +- 115070       6        good
android-chrome@4e4cf7775f                      18068249 +- 119990       9        good
android-chrome@5e7f0484c1                      18093460 +- 130192       6        good
android-chrome@5e7f0484c1,chromium@554232      18036450 +- 61396.6      6        good
android-chrome@5e7f0484c1,chromium@554266      17998397 +- 77571.0      6        good
android-chrome@5e7f0484c1,chromium@554276      18140843 +- 104569       6        good
android-chrome@5e7f0484c1,chromium@554279      18088337 +- 107452       6        good
android-chrome@5e7f0484c1,chromium@554280      ---                      ---      build failure
android-chrome@5e7f0484c1,chromium@554281      18536139 +- 173700       6        bad
android-chrome@5e7f0484c1,chromium@554282      18422055 +- 37594.2      6        bad
android-chrome@5e7f0484c1,chromium@554288      18399589 +- 83271.6      6        bad
android-chrome@5e7f0484c1,chromium@554305      18407671 +- 62185.3      6        bad
android-chrome@452ccfa0f7                      18549059 +- 170785       6        bad
android-chrome@0f6680b944                      18406176 +- 122353       6        bad
android-chrome@efed3974e3                      18398687 +- 109958       6        bad
android-chrome@d3db009934                      18402783 +- 57620.8      6        bad
android-chrome@061a8220c9                      18419121 +- 132603       6        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=load.search.taobao 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/8947464679960711792


For feedback, file a bug with component Speed>Bisection

WontFix-ing since this improved somewhat.