[Webkit-unassigned] [Bug 160160] New: [Threaded Compositor] Crashes and deadlocks in single web process mode

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jul 25 03:14:15 PDT 2016


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

            Bug ID: 160160
           Summary: [Threaded Compositor] Crashes and deadlocks in single
                    web process mode
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cgarcia at igalia.com
                CC: bugs-noreply at webkitgtk.org
            Blocks: 154066

Every WebPage has its own threaded compositor that runs its own compositing thread. That means that when there's more than one WebPage in the same process, we are running OpenGL stuff in different secondary threads. That's causing crashes and deadlocks in X and graphics drivers. We should ensure there's a single compositing thread per process. This is what is causing unit test WebKit2.WKPageGetScaleFactorNotZero to time out since we switched to the threaded compositor. That test is creating two pages in the same web process, and most of the times the web process crashes or deadlocks causing the test to never finish and time out.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160725/febf56e2/attachment.html>


More information about the webkit-unassigned mailing list