Webkit usually crashes when going directly to page 3 and looking around
I just starting using gallery and this crash has occurred with several versions.
I can't seem to get this to crash with r25150. Could you post a crashlog using the instructions on <http://webkit.org/quality/crashlogs.html>?
Created attachment 16027 [details] The last crash Last crash.... during gallery.mac.com
*** Bug 15112 has been marked as a duplicate of this bug. ***
I still can't reproduce this. See also bug 15087. And finally, pasting crashed thread stack trace for posterity: Thread 1 Crashed: 0 com.apple.WebCore 0x013b4a86 WebCore::ResourceHandle::client() const + 6 1 com.apple.WebCore 0x013b55ca -[WebCoreResourceHandleAsDelegate connection:willCacheResponse:] + 138 2 com.apple.Foundation 0x9287b713 -[NSURLConnection(NSURLConnectionInternal) _didFinishReturnCachedResponse:] + 615 3 com.apple.Foundation 0x9293a2a7 -[NSHTTPURLProtocol cachedResponseRevalidated:] + 68 4 com.apple.Foundation 0x92857272 -[NSConnectionHTTPURLProtocol attemptRetryAfter3xxResponse] + 630 5 com.apple.Foundation 0x92945047 -[NSConnectionHTTPURLProtocol performHTTPHeaderRead] + 827 6 com.apple.Foundation 0x92856a44 readStreamCallback2 + 495 7 com.apple.CoreFoundation 0x9087ab72 _CFStreamSignalEventSynch + 281 8 com.apple.CoreFoundation 0x9082cf92 CFRunLoopRunSpecific + 1213 9 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61 10 com.apple.Foundation 0x9282aa0f +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 259 11 com.apple.Foundation 0x927f52e0 forkThreadForFunction + 123 12 libSystem.B.dylib 0x90024227 _pthread_body + 84
It seems to crash very reliably at this url for me if I insert a "sleep(1);" at about line 478 of ResourceHandleMac.mm. between the: ++inNSURLConnectionCallback; and the: NSCachedURLResponse * newResponse = m_handle->client()->willCacheResponse(m_handle, cachedResponse); Note: using the browser like this is not fun. :)
I think this was fixed by Timothy Hatcher in <http://trac.webkit.org/projects/webkit/changeset/25777>. Please re-open if you still see this problem with newer nightly builds.
I concur that this was fixed in r25777.
*** Bug 15087 has been marked as a duplicate of this bug. ***
Per r25777: <rdar://problem/5199546>