Copy error, caused by: copy of X 0..1606 would end up overrunning the bounds of the Destination texture of X size 300

Happens if the canvas is created with one size, then resized.

We may need a test case here. One problem I see is that the CanvasContext recreates the SwapChain, but it doesn't tell anything to the old swapchain. So the old swapchain thinks that it's still usable, and any operations from the acquired frames are going to be failing.

Andrew, is this fixed by the recent canvas resizing work?

If I understand this issue correctly, it was a race between the old different sized swap chain calling back into the content process for presentation. We don't have this problem any more because the content process delegates to the compositor process completely for presentation aside from the CompositableHandle that binds the two in the display list processing.