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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/158ee3d0e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/158ee3d0e40000

Limit prefering glClear for clearing textures to macOS by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/7e86b9953779635b568e94d17deb5d4e2ab85287
6.347e+07 → 6.733e+07 (+3.862e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

When I enabled this patch, I got a bunch of Android regressions filed against it.

Now I've disabled it (in the above patch), and I get a bunch of Android regressions filed against it.

Since this is disabling a recently-added feature, closing as WontFix.