Pre-conditions: 1. Launch Reindeer Steps to reproduce: 1. Load www.cnn.com 2. Browser crashes and produces "App. closed: Reindeer" This is also reproducible on the latest Safari.
(In reply to comment #0) > This is also reproducible on the latest Safari. I'm not seeing this on a locally-built r15107 (with Patch v2 for Bug 9358). I haven't tried production Safari. Could you post a stack trace from the crash on Safari and/or Safari+WebKit?
(In reply to comment #1) > I haven't tried production Safari. Not seeing this on Safari 2.0.4 (419.3) on Mac OS X 10.4.7 (8J135/PowerPC) either.
I just built the latest safari at revision 15107 on Mac OS X version 10.4.6. This is still reproducible. - Load www.cnn.com - Takes around 30 seconds to load the page and then closes browser, displays a dialog "The application Safari quit unexpectedly".
(In reply to comment #3) > I just built the latest safari at revision 15107 on Mac OS X version 10.4.6. > This is still reproducible. > > - Load www.cnn.com > - Takes around 30 seconds to load the page and then closes browser, displays a > dialog "The application Safari quit unexpectedly". The stack trace would be very helpful. Did a "Crash Reporter" window come up after it quit unexpectedly? If so, copy and paste the contents of that window into this bug. Otherwise, the stack trace may be in this file in your home directory (near the "top" of the file): ~/Library/Logs/CrashReporter/Safari.crash.log
MacFixIt today also reports Safari crashing on cnn.com. No actual details given, just an advice to empty cache/delete cookies/delete com.apple.Safari.plist. Yes, a crash log would be extremely useful here.
Created attachment 9112 [details] cnn.com crash from Safari Here is the crash report from Safari.
(In reply to comment #6) > Created an attachment (id=9112) [edit] > cnn.com crash from Safari > > Here is the crash report from Safari. Thanks! It looks like you're using 10.4.6 on an Intel-based Mac, correct? Was this just Safari, or Safari+WebKit?
(In reply to comment #7) > (In reply to comment #6) > > Created an attachment (id=9112) [edit] > > cnn.com crash from Safari > > > > Here is the crash report from Safari. > Thanks! It looks like you're using 10.4.6 on an Intel-based Mac, correct? Was > this just Safari, or Safari+WebKit? Yes, I am using 10.4.6 on Intel-based Mac and Safari+Webkit.
There is probably a setTimeout() JavaScript method on the page that's firing and then doing something bad. Do you have pop-up blocking on (Cmd-K; see "Safari" menu)? I saw the page try to reload it self, I always see this at the bottom of the window (even on the initial page load) with pop-up blocking ON: Loading "http://www.cnn.com", completed 181 of 188 items I'm going to try turning pop-up blocking off to see if this causes a crash.
(In reply to comment #9) > I'm going to try turning pop-up blocking off to see if this causes a crash. No effect. For some reason, not all of the components on the page are getting loaded for me. Will post an image of the Activity window of the unloaded items.
Created attachment 9168 [details] Screen shot of Activity window with unloaded URLs
(In reply to comment #10) > No effect. For some reason, not all of the components on the page are getting > loaded for me. Will post an image of the Activity window of the unloaded > items. Note that I'm using a locally-built WebKit r15145 with a local patch for Bug 9179 and Safari 2.0.4 (419.3) on Mac OS X 10.4.7 (8J135/PowerPC) to test this.
the webkit crash is represented by this radar. <rdar://problem/4605532>
(In reply to comment #13) > the webkit crash is represented by this radar. <rdar://problem/4605532> A speculative fix was checked in as Subversion revision r15193. Krishna, please check a WebKit nightly build on r15193 or later to see if this fixes the problem for you.
(In reply to comment #14) > (In reply to comment #13) > > the webkit crash is represented by this radar. <rdar://problem/4605532> > A speculative fix was checked in as Subversion revision r15193. Krishna, > please check a WebKit nightly build on r15193 or later to see if this fixes the > problem for you. This is working fine, able to load www.cnn.com much quickly than earlier and no crash found. Verified at revision 15210.
(In reply to comment #15) > This is working fine, able to load www.cnn.com much quickly than earlier and no > crash found. Verified at revision 15210. RESOLVED/FIXED for WebKit ToT. Krishna, how do you want to handle the S60 bug? Do you want to open a different bug, or change this back to an S60-only bug?
(In reply to comment #16) > (In reply to comment #15) > > This is working fine, able to load www.cnn.com much quickly than earlier and no > > crash found. Verified at revision 15210. > RESOLVED/FIXED for WebKit ToT. Krishna, how do you want to handle the S60 > bug? Do you want to open a different bug, or change this back to an S60-only > bug? I think it is better to have the same bug and we will add PlatformOnly keyword to the Keywords field.
OK, doing that then.
seems fine now, i think either CNN fixed it or the latest nightly fixed it
Bulk update of s60 bugs - tagging and closing.
Bulk closing of all s60 platform bugs. Sorry for the noise!
re-purposing InTSW keyword for use by QtWebkit team