Bug 29926

Summary: http/tests/workers/text-encoding.html crashed on Leopard bot
Product: WebKit Reporter: Eric Seidel (no email) <eric>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, atwilson, dimich, levin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
crash dump from crash none

Eric Seidel (no email)
Reported 2009-09-30 08:26:10 PDT
http/tests/workers/text-encoding.html crashed on Leopard bot https://bugs.webkit.org/show_bug.cgi?id=29736#c10 I'll attach the crash dump.
Attachments
crash dump from crash (55.46 KB, text/plain)
2009-09-30 08:26 PDT, Eric Seidel (no email) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2009-09-30 08:26:56 PDT
Created attachment 40374 [details] crash dump from crash
Eric Seidel (no email)
Comment 2 2009-09-30 08:28:23 PDT
The crash was: Thread 15 Crashed: 0 ??? 0x1c29b900 0 + 472496384 1 com.apple.WebCore 0x01d448e2 WebCore::WorkerRunLoop::runInMode(WebCore::WorkerContext*, WebCore::String const&) + 114 (WorkerRunLoop.cpp:162) 2 com.apple.WebCore 0x01d47cea WebCore::WorkerThreadableLoader::loadResourceSynchronously(WebCore::WorkerContext*, WebCore::ResourceRequest const&, WebCore::ThreadableLoaderClient&, WebCore::ThreadableLoaderOptions const&) + 202 (WorkerThreadableLoader.cpp:79) 3 com.apple.WebCore 0x01d4d5c8 WebCore::XMLHttpRequest::createRequest(int&) + 1032 (XMLHttpRequest.cpp:493) Looks like it's grabbing at freed memory: Exception Codes: KERN_INVALID_ADDRESS at 0x000000002e035944 Not sure who to CC here.
Eric Seidel (no email)
Comment 3 2009-09-30 15:56:23 PDT
This timed out on the Tiger bot today too: http://build.webkit.org/results/Tiger%20Intel%20Release/r48914%20(4778)/results.html I assume the crash and timeout are related.
Ahmad Saleem
Comment 4 2023-12-26 07:15:38 PST
We don't have any platform specific expectation for this test, so marking this as 'RESOLVED CONFIGURATION CHANGED'.
Note You need to log in before you can comment on or make changes to this bug.