Chrome Version: 63.0.3239.26
OS: ChromeOS Panther

What steps will reproduce the problem?
(1) Open the Chromoting web-app and full-screen the window.
(2) Open Task Manager and note the Chromoting app's GPU memory usage.
(3) Connect to a host. Note the GPU memory usage.
(4) Disconnnect and reconnect a few times, to note the changes in GPU memory between connected & disconnected.
(5) Minimize the Chromoting window while connected. Note the GPU memory usage.
(6) Resize the window to 1/4 of a monitor. Note the GPU memory usage.
(7) Connect & disconnect as before, noting the GPU memory usage.

What is the expected result?

Expect that GPU memory usage is "reasonable" given the size of the remote desktop, e.g. within 2-4x the minimum memory required, for a single copy of the desktop contents.

Expect that when minimized the majority of the GPU memory is dropped.

What happens instead?

Chromoting consumes ~10x the "minimum" GPU memory usage, whether minimized or not, and gains 2-3x when visible.

My testing was with desktop dimensions of roughly 1920x1100@32bpp, i.e. ~8MiB for a single copy, and the CRD process' GPU memory grew by 90MiB while connected but minimized, and by a further 20-25MiB while visible.