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

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


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/14e6f9f6540000

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

[mojo] Per-message dispatch tasks by rockot@google.com
https://chromium.googlesource.com/chromium/src/+/471aa794bbb9e3a98542ee2135ea61ddf4bf87a3
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 1.579e+07 → 1.773e+07 (+1.947e+06)

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

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