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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_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/11cd6537640000

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

[embed handlers] Enable embedding of handlers by default by delphick@chromium.org
https://chromium.googlesource.com/v8/v8/+/6041afe4e98f562d2ae514fa329e0186737e2242
1.327e+07 → 1.393e+07 (+6.538e+05)

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

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

Looks like the space increase is in Large Object space, which my CL does not change at all. The graphs show that there's a near bimodal fluctuation from 0MB to 1.5MB introduce not long before my CL. Then my CL or one submitted near mine possibly made a flaky size increase consistent.

Later on another change reduces the memory increase significantly.

Overall I don't this reflects a real problem.