RESOLVED FIXED 42356
WebKitTestRunner and WebProcess simultaneously stall in CoreIPC::Connection::sendOutgoingMessage 
https://bugs.webkit.org/show_bug.cgi?id=42356
Summary WebKitTestRunner and WebProcess simultaneously stall in CoreIPC::Connection::...
Maciej Stachowiak
Reported 2010-07-15 03:56:46 PDT
WebKitTestRunner and WebProcess simultaneously stall in CoreIPC::Connection::sendOutgoingMessage. This can be reproduced running WebKitTestRunner on the following tests: fast/frames/cached-frame-counter.html fast/frames/sandboxed-iframe-navigation-parent.html Both processes appear to be trying to send each other a mach message and are stuck.
Attachments
Sample of the Web process (2.37 KB, text/plain)
2010-07-15 03:57 PDT, Maciej Stachowiak 		no flags
Details
Sample of the UI process (1.87 KB, text/plain)
2010-07-15 03:57 PDT, Maciej Stachowiak 		no flags
Details
Patch (10.04 KB, patch)
2010-07-19 18:53 PDT, Anders Carlsson 		sam: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Maciej Stachowiak
Comment 1 2010-07-15 03:57:28 PDT
Created attachment 61635 [details] Sample of the Web process
Maciej Stachowiak
Comment 2 2010-07-15 03:57:56 PDT
Created attachment 61636 [details] Sample of the UI process
Maciej Stachowiak
Comment 3 2010-07-15 04:10:36 PDT
<rdar://problem/8194511>
Anders Carlsson
Comment 4 2010-07-19 18:53:59 PDT
Created attachment 62025 [details] Patch
WebKit Review Bot
Comment 5 2010-07-19 18:57:07 PDT
Attachment 62025 [details] did not pass style-queue: Failed to run "['WebKitTools/Scripts/check-webkit-style']" exit_code: 1 WebKit2/Platform/mac/MachUtilities.cpp:26: Found header this file implements before WebCore config.h. Should be: config.h, primary header, blank line, and then alphabetically sorted. [build/include_order] [4] Total errors found: 1 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
Anders Carlsson
Comment 6 2010-07-19 19:43:28 PDT
Committed r63708: <http://trac.webkit.org/changeset/63708>
Note You need to log in before you can comment on or make changes to this bug.