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

[bugzilla-daemon at webkit.org]

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





--- Comment #3 from Vangelis Kokkevis <vangelis at chromium.org>  2011-04-04 22:38:32 PST ---
(In reply to comment #2)
> 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.

I'm not sure I see how LayerRendererChromium::create() can re-enter WebViewImpl::graphicsContext3D but I do agree that if that's possible your fix is necessary.  Have you been able to trace the calling sequence that results in the re-entrancy?

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