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

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


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

Win 7 Nvidia GPU 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/1284a996e40000

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

Bind canvas color management to GPU compositing by zakerinasab@chromium.org
https://chromium.googlesource.com/chromium/src/+/37aab329373b49a9753c0481e22c192f21861edd
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 3.604e+06 → 4.719e+06 (+1.114e+06)

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

Benchmark documentation link:
  None

This CL only introduces a guard for the new color managed canvas behavior which is still not shipped, and also generally should decrease the memory usage by falling back to legacy behavior (uint8 pixel format instead float16). I don't think it can be responsible for this regression.

Available, but no owner or component? Please find a component, as no one will ever find this without one.