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

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


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

Android Nexus5X WebView Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16f7ff30e40000

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

Paint timing: revert back to swap-time by npm@chromium.org
https://chromium.googlesource.com/chromium/src/+/f962a47e219a605eb9648251df3d76471fe06bd9
1.157e+07 → 1.19e+07 (+3.289e+05)

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

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16005e28e40000

I don't think the bisect is correct, trying again. Sadly it'll be hard because graph is so noisy now. It's worth noting that both graphs show dips before so this might just be related to reverting incorrect behavior.

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16005e28e40000

Paint timing: revert back to swap-time by npm@chromium.org
https://chromium.googlesource.com/chromium/src/+/f962a47e219a605eb9648251df3d76471fe06bd9
memory:webview:all_processes:reported_by_chrome:v8:effective_size: 1.156e+07 → 1.185e+07 (+2.909e+05)

Define basic Trichrome build targets. by torne@google.com
https://chromium.googlesource.com/chromium/src/+/bef92b9197b49def215aced79961f50e3b83544e
memory:webview:all_processes:reported_by_chrome:v8:effective_size: 1.185e+07 → No values

Revert "Define basic Trichrome build targets." by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/f505cde61a75f566b4edd2043015a93e5568f970
memory:webview:all_processes:reported_by_chrome:v8:effective_size: No values → 1.186e+07

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

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

 Issue 891233  has been merged into this issue.

Recovered.