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

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


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

Android Nexus5X WebView Perf
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/11f5a218e40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11f5a218e40000

[perf] Add browse:news:nytimes:2018 system health story by cbruni@chromium.org
https://chromium.googlesource.com/chromium/src/+/d41120d33ba8b51814a8305238bd903f42ee5b73
memory:webview:all_processes:reported_by_chrome:v8:allocated_objects_size: 6.395e+06 → 6.382e+06 (-1.237e+04)

[perf] Use EnterText for login helpers by cbruni@chromium.org
https://chromium.googlesource.com/chromium/src/+/05d3beb82456be9b199e9df8b3a93895a44201dc
memory:webview:all_processes:reported_by_chrome:v8:allocated_objects_size: 6.382e+06 → 6.57e+06 (+1.876e+05)

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

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

EnterText now emits separate keyboard events for every character in the input string. Most likely this caused some regression on the websites by invoking additional event handlers.

Hence I think this is working as intended.