washingtonpost.com crashes Safari

[LeeTom]

Hi,
Lately, when I read some stories at washingtonpost.com, Safari crashes. It never happens on the main page, but just after a story page loads. Does this happen to anyone else? It's been happening for a few weeks now, and has become more regular.

Here is part of the crash report, in case anyone knows what the hell it means:
(please don't quote this, pretty long!)

Date/Time: 2004-08-11 12:15:26 -0700
OS Version: 10.3.5 (Build 7M34)
Report Version: 2

Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Version: 1.2.3 (125.9)
PID: 391
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xfc000000

Thread 0 Crashed:
0 <<00000000>> 0xfc000000 0 + 0xfc000000
1 com.apple.WebCore 0x94f6e720 KHTMLPart::checkEmitLoadEvent() + 0x1c4
2 com.apple.WebCore 0x94f762e8 KHTMLPart::slotFinishedParsing() + 0x30
3 com.apple.WebCore 0x94f3f408 KWQSignal::call() const + 0x7c
4 com.apple.WebCore 0x94f3f408 KWQSignal::call() const + 0x7c
5 com.apple.WebCore 0x94f99644 HTMLTokenizer::finish() + 0x254
6 com.apple.WebCore 0x94f82d10 KHTMLPart::end() + 0x78
7 com.apple.WebKit 0x953034b0 -[WebFrame(WebPrivate) _isLoadComplete] + 0x208
8 com.apple.WebKit 0x95306250 +[WebFrame(WebPrivate) _recursiveCheckCompleteFromFrame:] + 0x78
9 com.apple.WebKit 0x95305f9c -[WebSubresourceClient connectionDidFinishLoading:] + 0x6c
10 com.apple.Foundation 0x90a3d4b4 -[NSURLConnection(NSURLConnectionInternal) _sendDidFinishLoadingCallback] + 0x4c
11 com.apple.Foundation 0x90a0c9ec -[NSURLConnection(NSURLConnectionInternal) _sendCallbacks] + 0x1f8
12 com.apple.Foundation 0x909f707c -[NSArray makeObjectsPerformSelector:withObject:] + 0x108
13 com.apple.Foundation 0x90a21214 _sendCallbacks + 0xd4
14 com.apple.CoreFoundation 0x90193d38 __CFRunLoopDoSources0 + 0x1fc
15 com.apple.CoreFoundation 0x901915f0 __CFRunLoopRun + 0x1b0
16 com.apple.CoreFoundation 0x90195f1c CFRunLoopRunSpecific + 0x148
17 com.apple.HIToolbox 0x927d5f88 RunCurrentEventLoopInMode + 0xac
18 com.apple.HIToolbox 0x927dc6f0 ReceiveNextEventCommon + 0x17c
19 com.apple.HIToolbox 0x927fe6c8 BlockUntilNextEventMatchingListInMode + 0x60
20 com.apple.AppKit 0x92dd227c _DPSNextEvent + 0x180
21 com.apple.AppKit 0x92de8c24 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74
22 com.apple.Safari 0x0000be30 0x1000 + 0xae30
23 com.apple.AppKit 0x92dfcf8c -[NSApplication run] + 0x21c
24 com.apple.AppKit 0x92eb948c NSApplicationMain + 0x1d0
25 com.apple.Safari 0x0000cfac 0x1000 + 0xbfac
26 com.apple.Safari 0x0000ce20 0x1000 + 0xbe20

Thread 1:
0 libSystem.B.dylib 0x900074c8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007018 mach_msg + 0x38
2 com.apple.CoreFoundation 0x90191790 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x90195f1c CFRunLoopRunSpecific + 0x148
4 com.apple.Foundation 0x909fc850 -[NSRunLoop runMode:beforeDate:] + 0xac
5 com.apple.Foundation 0x90a15454 -[NSRunLoop run] + 0x4c
6 com.apple.WebKit 0x953158bc +[WebFileDatabase _syncLoop:] + 0xa8
7 com.apple.Foundation 0x90a39b74 forkThreadForFunction + 0x6c
8 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 2:
0 libSystem.B.dylib 0x900074c8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007018 mach_msg + 0x38
2 com.apple.CoreFoundation 0x90191790 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x90195f1c CFRunLoopRunSpecific + 0x148
4 com.apple.Foundation 0x909fc850 -[NSRunLoop runMode:beforeDate:] + 0xac
5 com.apple.Foundation 0x90a15454 -[NSRunLoop run] + 0x4c
6 com.apple.Foundation 0x90a6747c +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 0x20c
7 com.apple.Foundation 0x90a39b74 forkThreadForFunction + 0x6c
8 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 3:
0 libSystem.B.dylib 0x9000b20c select + 0xc
1 com.apple.Foundation 0x909f205c _loadRunLoop + 0xd4
2 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 4:
0 libSystem.B.dylib 0x900074c8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007018 mach_msg + 0x38
2 com.apple.CoreFoundation 0x90191790 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x90195f1c CFRunLoopRunSpecific + 0x148
4 com.apple.Foundation 0x909fc850 -[NSRunLoop runMode:beforeDate:] + 0xac
5 com.apple.Foundation 0x90a15454 -[NSRunLoop run] + 0x4c
6 com.apple.Foundation 0x90a679bc +[NSURLCache _diskCacheSyncLoop:] + 0xa8
7 com.apple.Foundation 0x90a39b74 forkThreadForFunction + 0x6c
8 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 5:
0 libSystem.B.dylib 0x9000b20c select + 0xc
1 com.apple.CoreFoundation 0x90196ba0 __CFSocketManager + 0x1fc
2 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 6:
0 libSystem.B.dylib 0x90016f48 semaphore_wait_signal_trap + 0x8
1 libSystem.B.dylib 0x9000e790 _pthread_cond_wait + 0x270
2 com.apple.Foundation 0x90a4bb00 -[NSConditionLock lockWhenCondition:] + 0x44
3 com.apple.AppKit 0x92dca11c -[NSUIHeartBeat _heartBeatThread:] + 0x190
4 com.apple.Foundation 0x90a39b74 forkThreadForFunction + 0x6c
5 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

Thread 7:
0 libSystem.B.dylib 0x900074c8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007018 mach_msg + 0x38
2 ...ple.CoreServices.CarbonCore 0x9031a81c TS_exception_listener_thread + 0x70
3 libSystem.B.dylib 0x900246e8 _pthread_body + 0x28

PPC Thread State:
srr0: 0xfc000000 srr1: 0x4200f030 vrsave: 0x00000000
cr: 0x24004242 xer: 0x00000003 lr: 0x95055fa0 ctr: 0xfc000000
r0: 0x95055f44 r1: 0xbfffe4f0 r2: 0x08006f7b r3: 0x021cfa00
r4: 0x00000000 r5: 0x00000000 r6: 0x950cf8d8 r7: 0x00000001
r8: 0x00000001 r9: 0x00000000 r10: 0x00000001 r11: 0xa7313120
r12: 0xfc000000 r13: 0x00000000 r14: 0x00000000 r15: 0x00000001
r16: 0x00000000 r17: 0xbffff610 r18: 0x00000000 r19: 0x00000000
r20: 0x00007fe3 r21: 0xa09fc7f4 r22: 0xa09fc7f4 r23: 0xa09fc7f4
r24: 0xa09fc7f4 r25: 0x07c415a0 r26: 0xbfffe5c0 r27: 0xbfffe608
r28: 0x00000001 r29: 0x021cfa40 r30: 0x021cfa00 r31: 0x95055d9c


Thanks,
Lee Tom

[allroy]

have you emptied cache, got rid of preferences, all that stuff?
I check it out all the time and never had a problem.

What about using other browsers to test and see if they crash?

[Frobozz]

Hi,
Lately, when I read some stories at washingtonpost.com, Safari crashes. It never happens on the main page, but just after a story page loads. Does this happen to anyone else? It's been happening for a few weeks now, and has become more regular.

Here is part of the crash report, in case anyone knows what the hell it means:
(please don't quote this, pretty long!)

Thanks,
Lee Tom

If you are encountering certain types of advertisements that run unsupported Java commands, or heavy DHTMl/JS based navigation and/or ads I would expect this behavior. Safari has a pretty slow JS interpreter, and it seems that (until recently) it's support of Java was less than ideal.

[LeeTom]

It has crashed very soon after I've "Reset Safari...", so cache etc. shouldn't be a problem.

I will browse it in Firefox and see if anything happens. I have a feeling it may be one of the ads that comes up that Safari doesn't like.

Lee Tom

[MisterMe]

If you are encountering certain types of advertisements that run unsupported Java commands, or heavy DHTMl/JS based navigation and/or ads I would expect this behavior. Safari has a pretty slow JS interpreter, and it seems that (until recently) it's support of Java was less than ideal.Java support is not built into Safari, Java support is built into MacOS X 10.3. The MacOS X version of Java is one of the most standards-compliant version of Java there is. Problems may arise, however, when webpage designers use non-standard versions of Java that are optimized for Windows. Having experienced a crash on the Washington Post's website for myself, it appears to be caused by the animation in one of the ads. The problem does not appear to be caused by the content.