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

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


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

perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : James Darpinian
  Commit : d1b4ae2892b05cf622b3f649cb38b995ed2d1733
  Date   : Tue Jun 19 19:49:08 2018
  Subject: GPU: Don't flush when destroying transfer buffers.

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/load_chrome/load_chrome_blank
  Change       : 1600.00% | 131072.0 -> 2228224.0

Revision                                       Result              N
android-chrome@d79bf90511                      131072 +- 0.0       6      good
android-chrome@e90c9c80c5                      131072 +- 0.0       6      good
android-chrome@a5a5234c1c                      131072 +- 0.0       6      good
android-chrome@033c1f27dc                      131072 +- 0.0       6      good
android-chrome@edaff75ef5                      131072 +- 0.0       6      good
android-chrome@6bd07f8e66                      131072 +- 0.0       6      good
android-chrome@009b09f963                      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568439      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568524      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568566      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568572      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568574      131072 +- 0.0       6      good
android-chrome@009b09f963,chromium@568575      2228224 +- 0.0      6      bad       <--
android-chrome@009b09f963,chromium@568577      2228224 +- 0.0      6      bad
android-chrome@009b09f963,chromium@568587      2228224 +- 0.0      6      bad
android-chrome@6d7cb80987                      2228224 +- 0.0      6      bad
android-chrome@12fcaddca5                      2228224 +- 0.0      6      bad
android-chrome@8062d9e01c                      2228224 +- 0.0      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.chrome.blank 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/8942453485752393600


For feedback, file a bug with component Speed>Bisection