[Webkit-unassigned] [Bug 67281] New: The GDK lock is not held around GDK/GTK locks when they are from callbacks

[bugzilla-daemon at webkit.org]

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

           Summary: The GDK lock is not held around GDK/GTK locks when
                    they are from callbacks
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Major
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: yeh at lispworks.com


Created an attachment (id=105770)
 --> (https://bugs.webkit.org/attachment.cgi?id=105770&action=review)
Backtraces demonstarting GDK calls without GDK lock

The GDK lock is not held around GDK/GTK locks when they are from callbacks that are passed to soup functions.

For example, in the first backtrace gdk_window_invalidate_rect is called (it tails calls gdk_window_invalidate_rect_full, which is what you see in the backtrace). Nothing holds the lock at that point. 

In this backtrace WebCore is called Soup via the callback WebCore::readCallback. 

The second backtrace shows the same problem with a callback from a timeout vi WebCore::timeout_cb. The third backtrace is the same as the first. The fourth backtrace shows the same call to GDK, but via another route where the GDK lock is held. 

There was a discussion about this the webkit-gtk mailing list, subject is "What supposed to hold the GDK in calls from WebKit/gtk/WebCoreSupport":
https://lists.webkit.org/pipermail/webkit-gtk/2011-August/000645.html

See also https://bugs.webkit.org/show_bug.cgi?id=30876

Currently we cannot use webkitgtk, because we do multi-threading and without the lock it is not thread-safe.

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