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

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


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

perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 58c768b5f30324564a0178a2c1b7f7a88ccff352
  bad_revision : 5ec205887a0b04bb100bd3eb07b432c1b378367c

If failures persist 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:proportional_resident_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 1.01% | 76008137.3333 -> 76774316.8889

Revision                                       Result                  N
android-chrome@b50c37440c                      76008137 +- 506628      9        good
android-chrome@b50c37440c,chromium@560690      76192628 +- 381851      6        good
android-chrome@b50c37440c,chromium@560699      76684002 +- 295995      14       good
android-chrome@b50c37440c,chromium@560703      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560704      76325090 +- 286493      14       bad
android-chrome@b50c37440c,chromium@560707      76722694 +- 482511      14       bad
android-chrome@b50c37440c,chromium@560724      77067522 +- 310423      9        bad
android-chrome@3e4ba1f0ce                      77300425 +- 380640      6        bad
android-chrome@5c07f907f2                      76774317 +- 318020      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=http.www.amazon.com.gp.aw.s.k.nexus 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/8945072474372862416


For feedback, file a bug with component Speed>Bisection

This came back down.