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

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


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

perf-go-webview-phone

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

=== Auto-CCing suspected CL author ccameron@chromium.org ===

Hi ccameron@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Christopher Cameron
  Commit : fc70961580f6f6bd2498fd3242cb6ab35362cefc
  Date   : Tue Jun 05 01:08:16 2018
  Subject: Prefer to use glClear to clear uninitialized textures

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_search/load_search_baidu
  Change       : 3.82% | 7044095.33333 -> 7313066.0

Revision                                       Result                  N
android-chrome@d79bf90511                      7044095 +- 12058.3      6      good
android-chrome@50333525d6                      7035221 +- 23230.7      6      good
android-chrome@aeaee1eeb2                      7045461 +- 20832.0      6      good
android-chrome@2d0aa27954                      7023615 +- 6688.74      6      good
android-chrome@d46272ab3e                      7044095 +- 20343.0      6      good
android-chrome@d46272ab3e,chromium@564289      7027711 +- 27128.6      6      good
android-chrome@d46272ab3e,chromium@564307      7030442 +- 12952.7      6      good
android-chrome@d46272ab3e,chromium@564316      7046143 +- 28190.1      6      good
android-chrome@d46272ab3e,chromium@564321      7045461 +- 17506.1      6      good
android-chrome@d46272ab3e,chromium@564323      7036586 +- 30182.8      6      good
android-chrome@d46272ab3e,chromium@564324      7296682 +- 21204.5      6      bad       <--
android-chrome@d46272ab3e,chromium@564325      7287125 +- 19153.6      6      bad
android-chrome@d46272ab3e,chromium@564361      7306922 +- 21164.9      6      bad
android-chrome@2385ec28b7                      7289173 +- 26597.7      6      bad
android-chrome@9d58762b56                      7307605 +- 24116.6      6      bad
android-chrome@824bd58772                      7298047 +- 16520.0      6      bad
android-chrome@37b5327f94                      7308287 +- 12800.7      6      bad
android-chrome@e90c9c80c5                      7301461 +- 17649.3      6      bad
android-chrome@8062d9e01c                      7313066 +- 16587.5      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.baidu 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/8941357759999937152


For feedback, file a bug with component Speed>Bisection