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

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


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

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

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

memory.top_10_mobile - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12f24112e40000

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

Revert "solid color quads workaround for use-zoom-for-dsf" by eirage@chromium.org
https://chromium.googlesource.com/chromium/src/+/d7d5990bc6b25d7b7ce711b035147030e778879a
memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size: 3.409e+07 → 3.692e+07 (+2.835e+06)

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

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

Strange that the revert would increase memory usage, but the landing <1 day ago did not decrease it. Re-running Pinpoint job to be sure...

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11a9aca2e40000

Actually I think the pinpoint is correct.
The workaround is for fixing the regressions with zoom-for-dsf. The zoom-for-dsf flag is turned on after I landed the workaround and before the revert. So the regressions appear once it's reverted. 

(The proper fix for the regression is in progress.)

 Issue 893601  has been merged into this issue.

 Issue 893868  has been merged into this issue.

 Issue 894118  has been merged into this issue.

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

Revert "solid color quads workaround for use-zoom-for-dsf" by eirage@chromium.org
https://chromium.googlesource.com/chromium/src/+/d7d5990bc6b25d7b7ce711b035147030e778879a
memory:webview:all_processes:reported_by_chrome:malloc:allocated_objects_size: 4.796e+07 → 4.843e+07 (+4.705e+05)

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

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