Don't force rendering in finishAllRendering
authorpiman@chromium.org <piman@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Mon, 21 May 2012 22:57:49 +0000 (22:57 +0000)
committerpiman@chromium.org <piman@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Mon, 21 May 2012 22:57:49 +0000 (22:57 +0000)
commit44e597b32a94374916e8ceceae3f10c5130cc4bb
treec45f9d9c2b7cccba6f63b4e3f77fc40ed8168e23
parent19c0e7ab22cfd24dbf143c4039217a7ed513d721
Don't force rendering in finishAllRendering
https://bugs.webkit.org/show_bug.cgi?id=86919

Reviewed by James Robinson.

After we acquire the texture layers on the main thread, we can't draw.
In particular if we destroyed the texture ids used previously by
TextureLayerChromium, drawing before a commit would cause a
bind-after-destroy.

Tested by CCLayerTreeHostTestFinishAllRendering.

* platform/graphics/chromium/cc/CCThreadProxy.cpp:
(WebCore::CCThreadProxy::CCThreadProxy):
(WebCore::CCThreadProxy::finishAllRenderingOnImplThread):
(WebCore::CCThreadProxy::scheduledActionDrawAndSwapInternal):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@117825 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/platform/graphics/chromium/cc/CCThreadProxy.cpp
Source/WebKit/chromium/tests/CCLayerTreeHostTest.cpp