Technically I think a 256x256 canvas is the minimum to trigger the bug (otherwise the canvas does not get hardware accelerated and takes a different copy path.) I didn't want to hit it right on the edge, though, just in case Chrome changes it's HW acceleration metrics in the future.