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

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


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

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/13ba5039940000

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

[PE] Set GraphicsLayerUpdate bits on the enclosing stacking composited layer. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/722a913a012145a221973945fd9411ad6444ccd2
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 7.077e+07 → 7.339e+07 (+2.623e+06)

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

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

This is caused by a necessary fix for correctness.