[Webkit-unassigned] [Bug 81954] [Chromium] Using WebViewPlugins with --force-compositing-mode causes an ASSERT to fail

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Mar 22 14:19:43 PDT 2012


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





--- Comment #5 from Fady Samuel <fsamuel at chromium.org>  2012-03-22 14:19:43 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > To expand a bit, WebViewPlugin is a WebPlugin implementation that forwards drawing and input event handling to a separate WebView, to allow us to draw plug-in placeholders in HTML. The inner WebView is by design completely independent from the outer one (from the point of view of the outer one, it's just a plug-in), so it shouldn't be a problem that we call layout() on the inner one during paint() in the outer one. WebPlugin also doesn't have a layout() method, so we can't call layout() on the inner WebView when the outer one is being layouted.
> > 
> > Is the crash caused by the two RenderViews somehow sharing graphics layers? If so, maybe that's what we should prevent.
> 
> The problem here is s_inPaintContents is a static variable that's shared between the two WebView instances. One WebView is painting while the other is laying out.

How important is it that we keep this assert? It would be nice to debug in force-compositing-mode and not occasionally fire this assert when there's an old or missing plugin.

-- 
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