Chrome Version: 65.0.3299.0
OS: Chrome

What steps will reproduce the problem?
(0) Enable Out of Process heap profiling of the browser & GPU processes.
(1) Open crbug.com in a tab and click New Bug.
(3) Open Task Manager and sort by memory usage.
(4) Resize the crbug window back and forth (either vertically or horizontally).
(5) Move the crbug window around on the screen.

What is the expected result?

Expect that the window resizes & moves smoothly, even if the content itself fails to keep-up with the rate of resize.

What happens instead?

The entire UI will tend to hang for seconds at a time, when either moving or resizing (on a 4GB device).

When it starts updating again, the OOP profiler utility process has usually ballooned to a 1.5GB memory footprint.

It's not a huge surprise that resizing triggers some reallocations, but resizing & moving windows seem sufficiently common tasks that we should try to address this, if possible, to make OOP more widely useful.