If DrawingAreaImpl delays its exit from compositing (say if you change m_exitCompositingTimer.startOneShot() to use 3 seconds), then compositing layers stick around for that time, even after they should have been hidden.
Created attachment 82527 [details] Patch
Comment on attachment 82527 [details] Patch Does this mean we’ll see something different onscreen at the moment setRootCompositingLayer is called?
I think the zero-delay timer masked this issue, or at least just caused one frame of badness.
http://trac.webkit.org/changeset/78623