[Webkit-unassigned] [Bug 43506] http/tests/appcache/idempotent-update.html (or foreign-iframe-main.html?) occasionally crashes on Leopard Bot
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 4 14:27:15 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=43506
Alexey Proskuryakov <ap at webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|http/tests/appcache/idempot |http/tests/appcache/idempot
|ent-update.html |ent-update.html (or
|occasionally crashes on |foreign-iframe-main.html?)
|Leopard Bot |occasionally crashes on
| |Leopard Bot
Platform|PC |Macintosh
OS/Version|Mac OS X 10.5 |All
Priority|P2 |P1
CC| |beidson at apple.com,
| |mjs at apple.com
--- Comment #1 from Alexey Proskuryakov <ap at webkit.org> 2010-08-04 14:27:15 PST ---
I think it's actually foreign-iframe-main.html that crashes the next test. I could get it to assert with --repeat-each 10:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000bbadbeef
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.WebKit 0x00000001008be62d WebFrameLoaderClient::userAgent(WebCore::KURL const&) + 91 (WebFrameLoaderClient.mm:1281)
1 com.apple.WebCore 0x00000001011ce685 WebCore::FrameLoader::applyUserAgent(WebCore::ResourceRequest&) + 65 (FrameLoader.cpp:3117)
2 com.apple.WebCore 0x0000000100e55383 WebCore::ApplicationCacheGroup::createResourceHandle(WebCore::KURL const&, WebCore::ApplicationCacheResource*) + 109 (ApplicationCacheGroup.cpp:469)
3 com.apple.WebCore 0x0000000100e56975 WebCore::ApplicationCacheGroup::startLoadingEntry() + 487 (ApplicationCacheGroup.cpp:997)
4 com.apple.WebCore 0x0000000100e58e0c WebCore::ApplicationCacheGroup::didFinishLoading(WebCore::ResourceHandle*) + 672 (ApplicationCacheGroup.cpp:644)
5 com.apple.WebCore 0x00000001018791ad -[WebCoreResourceHandleAsDelegate connectionDidFinishLoading:] + 270 (ResourceHandleMac.mm:915)
...
This seems to mean that network loading didn't stop when a navigation happened, which may have far reaching consequences. I'm not sure if r40627 has anything to do with this.
This particular assertion doesn't mean immediately crashing in release mode, as there is an early return, but further processing of a spurious didFinishLoading can cause much badness.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list