The compositor has a TaskRunner that is not from the MessageLoop to pump things specially during resize.
However some parts of OutputSurface implementations are using ThreadTaskRunnerHandle::Get() to post tasks, instead of the compositor's TaskRunner, which bypasses this.
Places include:
SoftwareBrowserCompositorOutputSurface::SwapBuffers
OutputSurface::PostSwapBuffersComplete
So if the message loop is blocked, we won't hear about the swap being done, and we will throttle new frames, making things bad.
This probably will affect a lot more users when we make resizing better on windows.
Comment 1 by danakj@chromium.org
, Jun 3 2016