[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:24:59 PDT 2012


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





--- Comment #7 from James Robinson <jamesr at chromium.org>  2012-03-22 14:24:59 PST ---
It's very important for the normal case where there's one compositing tree in the process and mutating it is a sign of either concurrent access from multiple threads (always bad) or something mutating layout inside a WebView while that WebView is being painted.

You could make this restriction per-WebView if you wanted isolation here.  I would not be OK with turning the ASSERT() off completely, it's helped us catch many other bugs.

Or just do layout inside the WebView at the same time inside the WebViewPlugin as outside the WebView if you are painting them in lockstep, which it appears from this callstack that you are.

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