[Webkit-unassigned] [Bug 57812] Re-entrancy issue with setIsAcceleratedCompositingActive

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 4 21:44:53 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=57812


Antoine Labour <piman at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         OS/Version|Mac OS X 10.5               |All




--- Comment #2 from Antoine Labour <piman at chromium.org>  2011-04-04 21:44:54 PST ---
http://code.google.com/p/chromium-os/issues/detail?id=13821 shows this issue. In chrome, LayerRendererChromium::create might re-enter WebViewImpl::graphicsContext3D, but at that point m_temporaryOnscreenGraphicsContext3D is already reset, whereas m_layerRenderer is not set yet. So we end up creating a new context that isn't used by the compositor, and we then give the compositor a texture ID that doesn't belong to the right context.
This patch makes sure we only reset m_temporaryOnscreenGraphicsContext3D after m_layerRenderer has been set.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list