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

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


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

Android Nexus5 Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14c48807e40000

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

cc: Avoid acquiring the context lock if unnecessary. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/5d4e09620ff79ac668c72ad3677f993b75e617ce
memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size: 7.074e+07 → 8.666e+07 (+1.593e+07)

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

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

A bug in the previous change: https://chromium.googlesource.com/chromium/src/+/cd8fbb77cfa164eef66378204a588443af9bb875 caused the improvement which was lost by the fix in this change.