Bug 9324

Summary: Crashes when visiting Westlaw law school welcome page
Product: WebKit Reporter: David Tannenbaum <david.tannenbaum>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: adam.hansen, ian, lars, webkit
Priority: P2    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://lawschool.westlaw.com/DesktopDefault.aspx
Attachments:
Description Flags
Crash reporter from visit to Westlaw law school home page none

Description David Tannenbaum 2006-06-05 22:47:26 PDT
Frequently, but not always, Webkit immediately crashes when I visit this URL.
Comment 1 David Kilzer (:ddkilzer) 2006-06-06 04:08:59 PDT
Reporter, please post a stack trace of the crash when it occurs.  Just copy and paste everything from the crash dialog that asks you to report it to Apple into a comment on this bug, or save it to a text file and post it as an attachment.  Thanks!
Comment 2 David Kilzer (:ddkilzer) 2006-06-06 04:10:23 PDT
Also, please note if you have any Safari extensions installed.  (If you do, please retest with them disabled or uninstalled since they are a frequent cause of crashes.)
Comment 3 David Tannenbaum 2006-06-06 09:13:05 PDT
Created attachment 8728 [details]
Crash reporter from visit to Westlaw law school home page
Comment 4 David Tannenbaum 2006-06-06 09:15:08 PDT
(In reply to comment #2)
> Also, please note if you have any Safari extensions installed.  (If you do,
> please retest with them disabled or uninstalled since they are a frequent cause
> of crashes.)
> 

What counts as a Safari extension? A Flash plug-in, for example?
Comment 5 David Kilzer (:ddkilzer) 2006-06-06 10:13:12 PDT
(In reply to comment #4)
> What counts as a Safari extension? A Flash plug-in, for example?

No, plug-ins like Flash that use a well-documented API are okay.

Most (if not all) of the extensions found at Pimp My Safari (http://pimpmysafari.com/) can cause random crashes and should be avoided when testing WebKit nightlies (or production Safari releases, for that matter).
Comment 6 David Tannenbaum 2006-06-06 14:01:50 PDT
> Most (if not all) of the extensions found at Pimp My Safari
> (http://pimpmysafari.com/) can cause random crashes and should be avoided when
> testing WebKit nightlies (or production Safari releases, for that matter).

Got it. As far as I know I do not have any extensions installed.
Comment 7 David Kilzer (:ddkilzer) 2006-06-06 14:25:56 PDT
(In reply to comment #6)
> Got it. As far as I know I do not have any extensions installed.

They tend to show up in the stack traces as well.  The one you posted looks clean.  :)
Comment 8 David Kilzer (:ddkilzer) 2006-06-06 14:28:21 PDT
David, can you also note which nightly you used (rNNNNN) to get the errors?  Thanks!
Comment 9 David Tannenbaum 2006-06-06 17:59:20 PDT
(In reply to comment #8)
> David, can you also note which nightly you used (rNNNNN) to get the errors? 
> Thanks!
> 

How do I figure that out? I can tell you that I downloaded it on June 3rd.
Comment 10 David Kilzer (:ddkilzer) 2006-06-06 19:12:20 PDT
(In reply to comment #9)
> How do I figure that out? I can tell you that I downloaded it on June 3rd.

The name of the .dmg file contains the revision, e.g. WebKit-SVN-r14704.dmg, if you kept the original filename.
Comment 11 Lars Næsbye Christensen 2006-10-01 22:19:34 PDT
The URL does not seem to make the nightly r16703 crash.
Comment 12 Adam Hansen 2007-07-11 09:07:50 PDT
Works for me when using Safari 2.0.4 (419.3), Safari 3.0.2 (522.12), and WebKit r24182.
Comment 13 Robert Blaut 2008-02-20 14:44:03 PST
I also cannot confirm the crash bug. Per comment #11, comment #12 and my tests I mark the bug report as WORKSFORME. 

David, feel free to reopen if you still experiences crashes in the latest Webkit nightly.