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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149d4a8be40000

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

[media] Enable MojoVideoDecoder by default. by sandersd@chromium.org
https://chromium.googlesource.com/chromium/src/+/44323658c5cc4fff0a2d4a0bcd1d4aa9a7290c87
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 2.448e+07 → 1.118e+07 (-1.329e+07)

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

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

Seems to be the opposite of the increases alerted yesterday, apparently memory usage moved away from the GPU process.