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

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


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

Android Nexus6 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/1496e389940000

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

Explicitly say what sequence Mojo callbacks run on by amoylan@chromium.org
https://chromium.googlesource.com/chromium/src/+/9216d3771164323a12575c627ba9368086bfdd7e
memory:webview:all_processes:reported_by_chrome:malloc:effective_size: 2.451e+07 → 2.424e+07 (-2.768e+05)

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

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

This is just a README.md file update.

Thanks amoylan@ and sorry about the false alert.

It seems that the regression should be nudged +1. I kicked a wider bisect. If it does not find anything we should close.

Assigned, but no owner or component? Please find a component and/or owner