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

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


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

Win 7 Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16173723e40000

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

Use RasterDecoder for CPU raster by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/8e4f35d1fe31c1b0b8f0123a10d498f0139b9097
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 2.778e+08 → 2.819e+08 (+4.033e+06)

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

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

I'm guessing that this was fixed by https://chromium-review.googlesource.com/c/chromium/src/+/1299601

The graphs do not show any data since after that CL landed. I'm guessing that as soon as they do, the regression will disappear.