[Webkit-unassigned] [Bug 11592] New: deadlock in UI between two threads trying to draw to screen

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 13 14:16:36 PST 2006


http://bugs.webkit.org/show_bug.cgi?id=11592

           Summary: deadlock in UI between two threads trying to draw to
                    screen
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: dwood at karelia.com


In my webkit-using app, I came across an interesting UI deadlock.  

The main thread, in my code, was calling
-[NSView displayIfNeeded]  -> -[NSViewHierarchyLock
lockForReadingWithExceptionHandler:] -> pthread_cond_wait ....

But there was another thread, spawned by
+[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] that was
responding to data being available in the webview -[WebMainResourceClient
didReceiveData:lengthReceived:]  that deadlocked with thread 1.

The backtrace from a sample will be attached as a sample since it won't
reproduce well in this text field.  

I have only had this happen once, unfortunately.  but maybe somebody can
understand why a backgrond thread is messing with the UI and locking with
thread 1.


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



More information about the webkit-unassigned mailing list