Bug 34039

Summary: REGRESSION(53714): WebKit crashes on any page
Product: WebKit Reporter: gdimatteo
Component: Web Template FrameworkAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, dimich, eric, giljanus
Priority: P1    
Version: 528+ (Nightly build)   
Hardware: Mac (PowerPC)   
OS: OS X 10.4   
Attachments:
Description Flags
copy/paste from Console.app
none
Crash log of r53757. none

gdimatteo
Reported 2010-01-23 07:28:36 PST
Webkit r53757 crashes with any page/site. I tried to delete the preferences plist files of both WebKit and Safari, tried with another account, with the same result. I can only start it with a blank page but as soon as I try to connect to any site it crashes. My system: Mac OS X 10.4.11 - iMac G4 PPC
Attachments
copy/paste from Console.app (14.47 KB, text/plain)
2010-01-23 07:30 PST, gdimatteo 		no flags
Details
Crash log of r53757. (19.85 KB, text/plain)
2010-01-23 14:02 PST, Gil Janus 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
gdimatteo
Comment 1 2010-01-23 07:30:18 PST
Created attachment 47272 [details] copy/paste from Console.app
Gil Janus
Comment 2 2010-01-23 14:02:25 PST
Created attachment 47278 [details] Crash log of r53757.
Gil Janus
Comment 3 2010-01-23 14:04:35 PST
I too had r53757 crash web visiting any webpage. Mac OS 10.4.11 - G4 PPC No Safari extensions.
Mark Rowe (bdash)
Comment 4 2010-01-23 14:47:39 PST
This is almost certainly due to r53714. Safari is calling WTF::detachThread which is crashing on Tiger in nightly builds for some reason after this change.
Alexey Proskuryakov
Comment 5 2010-01-23 20:55:57 PST
See also: bug 34045.
Alexey Proskuryakov
Comment 6 2010-01-25 16:01:46 PST
*** Bug 34045 has been marked as a duplicate of this bug. ***
Eric Seidel (no email)
Comment 7 2010-01-25 16:05:26 PST
Given this has a dupe, marking it as confirmed.
Alexey Proskuryakov
Comment 8 2010-01-25 16:10:38 PST
Fixed for me in r53815. Thank you for reporting this, please verify with a nightly build newer than 53815.
Note You need to log in before you can comment on or make changes to this bug.