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

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


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

memory.top_10_mobile - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10fb9eade40000

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

Reland "[blink] Control ScriptStreamer with ScriptResource" by leszeks@chromium.org
https://chromium.googlesource.com/chromium/src/+/dd9df78ccc1e1ac79a5657966a264562c6d03fb7
memory:webview:all_processes:reported_by_chrome:malloc:effective_size: 3.45e+07 → 3.489e+07 (+3.942e+05)

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

Benchmark documentation link:
  None

WAI I think, more streaming means more data passed to the background threads, so more memory. Eventually we may de-duplicate this data as part of other work, but for now closing as WontFix.

 Issue 902854  has been merged into this issue.