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

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


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

linux-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/119d0211e40000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/119d0211e40000

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

Bound time to delete cc::Resource by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf42619ce76159d90ab4b968208ad620c042ac2
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 2.793e+08 → 2.897e+08 (+1.045e+07)

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

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

I believe that this has been fixed on head as of October 30 and that the metrics just haven't caught up yet.