Summary: | REGRESSION: Assertion failure: !m_policyListener in WebFrameLoaderClient::setUpPolicyListener when re-sending form data | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | beidson, ddkilzer |
Priority: | P1 | Keywords: | InRadar, NeedsReduction, Regression |
Version: | 420+ | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
URL: | http://www.verticaladventures.org/trainingmanuals.cfm |
Description
Alexey Proskuryakov
2006-07-14 13:56:09 PDT
Even after all the refactoring, this bug still reproduces, although with a different assertion: ASSERTION FAILED: !m_policyListener (/Users/ap/WebKit/WebKit/WebCoreSupport/WebFrameLoaderClient.mm:1151 setUpPolicyListener) Thread 0 Crashed: 0 com.apple.WebKit 0x003d806c WebFrameLoaderClient::setUpPolicyListener(void (WebCore::FrameLoader::*)(WebCore::PolicyAction)) + 120 (WebFrameLoaderClient.mm:1151) 1 com.apple.WebKit 0x003d84bc WebFrameLoaderClient::dispatchDecidePolicyForMIMEType(void (WebCore::FrameLoader::*)(WebCore::PolicyAction), WebCore::String const&, WebCore::ResourceRequest const&) + 200 (WebFrameLoaderClient.mm:670) 2 com.apple.WebCore 0x0149094c WebCore::FrameLoader::checkContentPolicy(WebCore::String const&, void (*)(void*, WebCore::PolicyAction), void*) + 176 (FrameLoaderMac.mm:626) 3 com.apple.WebCore 0x01497494 WebCore::MainResourceLoader::didReceiveResponse(NSURLResponse*) + 784 (MainResourceLoaderMac.mm:299) 4 com.apple.WebCore 0x01493918 WebCore::ResourceLoader::didReceiveResponse(WebCore::ResourceHandle*, WebCore::ResourceResponse const&) + 80 (ResourceLoaderMac.mm:437) 5 com.apple.WebCore 0x014a8a2c -[WebCoreResourceHandleAsDelegate connection:didReceiveResponse:] + 164 (ResourceHandleMac.mm:268) 6 com.apple.Foundation 0x9298da2c -[NSURLConnection(NSURLConnectionInternal) _sendCallbacks] + 416 7 com.apple.Foundation 0x9298d810 _sendCallbacks + 156 Steps to reproduce: 1. Open http://www.verticaladventures.org/trainingmanuals.cfm 2. Enter something for the code, press Enter. 3. Dismiss an alert that appears. 4. Reload the page, click Cancel when asked about re-sending form data. 4. Reload the page again, click Resend this time. Results: the same sheet asking about re-sending form data appears again; then WebKit crashes with an assertion. Adding a NeedsRadar keyword, because the behavior is closely tied to Safari. Closed by accident, re-opening. *** Bug 12418 has been marked as a duplicate of this bug. *** I've been seeing this a lot recently when playing with the W3C HTML validator using this URL: http://validator.w3.org/#validate-by-upload See Bug 12418 for current assertion and stack trace. Steps to reproduce: 1. Open Safari/WebKit. 2. Open URL: http://validator.w3.org/ 3. Click "Choose File" in "Validate by File Upload" section and select an HTML file. 4. Click "Check" button. 5. Let page load, but DO NOT click anywhere in the page or scroll it. 6. Click "Reload" button in Safari. Expected results: Page should reload without crashing Safari/WebKit. Actual results: Safari/WebKit crashes with said assertion failure. Regression: This is a regression from shipping Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8N1037). Notes: Reproduced using a locally-built debug build of WebKit r19151 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8N1037). (In reply to comment #6) > Steps to reproduce: > > 1. Open Safari/WebKit. > 2. Open URL: http://validator.w3.org/ > 3. Click "Choose File" in "Validate by File Upload" section and select an HTML file. > 4. Click "Check" button. > 5. Let page load, but DO NOT click anywhere in the page or scroll it. > 6. Click "Reload" button in Safari. 7. Click "Send" on the "Are you sure you want to send a form again?" sheet. Note that a second sheet will appear, but Safari/WebKit will crash before you may click "Send". Bug 12417 is filed for the second sheet appearing. Closed in Radar; resolving This still happens for me; reopening. Chris Petersen is going to reopen the Radar bug, as well. Indeed, I can repro with the validator steps as well. Escalating to P1, since it blocks another P1 on the validator page. I can't reproduce this anymore, it was probably fixed by the fix to http://bugs.webkit.org/show_bug.cgi?id=12417 Still happens with slightly different steps to reproduce, see bug 14617. |