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

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


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

mac-10_12_laptop_low_end-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/147c9b2c140000

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

[v8] Add Mac to script streaming field trial by leszeks@chromium.org
https://chromium.googlesource.com/chromium/src/+/984c9422cefcd565e6ccef6a7316ba2488107e93
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 1.911e+08 → 1.976e+08 (+6.56e+06)

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

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

WAI, more compile tasks == more memory. Etienne, FYI in case scheduler team wants to add memory use to their scheduling heuristics.