Bug 55375

Summary: http/tests/websocket/tests/reload-crash.html sometimes crashes beneath SocketStreamHandle::readStreamCallback on Windows
Product: WebKit Reporter: Adam Roben (:aroben) <aroben>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: abarth, ap, bweinstein, yutak
Priority: P2 Keywords: InRadar, LayoutTestFailure, PlatformOnly
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   

Adam Roben (:aroben)
Reported 2011-02-28 07:31:23 PST
http/tests/websocket/tests/reload-crash.html sometimes crashes on Windows. Here are some crash logs: http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r79849%20(9839)/http/tests/websocket/tests/reload-crash-crash-log.txt http:// build.webkit.org/results/Windows%207%20Release%20(Tests)/r79855%20(9843)/http/tests/websocket/tests/reload-crash-crash-log.txt We're crashing beneath SocketStreamHandle::readStreamCallback. It looks like we trampoline this call over to the main thread; maybe the SocketStreamHandle has already been destroyed by the time the main thread runs the function?
Attachments
Adam Roben (:aroben)
Comment 1 2011-02-28 08:00:34 PST
Perhaps a duplicate of bug 44138?
Adam Roben (:aroben)
Comment 2 2011-02-28 08:05:54 PST
Added to the Skipped file in r79865.
Adam Roben (:aroben)
Comment 3 2011-02-28 08:06:29 PST
Adam Roben (:aroben)
Comment 4 2011-02-28 08:51:56 PST
In this slightly different crash log: http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r79864%20(9851)/http/tests/websocket/tests/reload-crash-crash-log.txt ...the crashing code is this: FAULTING_SOURCE_CODE: 523: length = CFReadStreamRead(m_readStream.get(), localBuffer, sizeof(localBuffer)); 524: ptr = localBuffer; 525: } 526: > 527: m_client->didReceiveData(this, reinterpret_cast<const char*>(ptr), length); 528: 529: break; 530: } 531: case kCFStreamEventCanAcceptBytes: 532: ASSERT_NOT_REACHED();
Alexey Proskuryakov
Comment 5 2011-03-14 14:44:13 PDT
*** This bug has been marked as a duplicate of bug 44138 ***
Note You need to log in before you can comment on or make changes to this bug.