[Doc HM]

I know that there have been some issues with Safa 3.2 crashing out, and indeed I have been experiencing this regularly on a 17in MacBook Pro. After downloading the latest update and seeing no improvement, I've been looking at the crash logs.

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 3

Here's the section for thread 3:

Thread 3 Crashed:
0 libSystem.B.dylib 0xffff0800 __memcpy + 96
1 com.apple.Safari 0x0013f200 0x1000 + 1303040
2 com.apple.Safari 0x00141237 0x1000 + 1311287
3 com.apple.Safari 0x0014785b 0x1000 + 1337435
4 com.apple.Safari 0x0018a7f3 0x1000 + 1611763
5 com.apple.Safari 0x00194772 0x1000 + 1652594
6 com.apple.Safari 0x00194e2d 0x1000 + 1654317
7 com.apple.Safari 0x00110c9b 0x1000 + 1113243
8 com.apple.Safari 0x00111034 0x1000 + 1114164
9 com.apple.Safari 0x001110a7 0x1000 + 1114279
10 com.apple.Safari 0x00111313 0x1000 + 1114899
11 com.apple.Safari 0x001115f8 0x1000 + 1115640
12 com.apple.Safari 0x001184a3 0x1000 + 1143971
13 com.apple.CoreFoundation 0x96aac65f CFRunLoopRunSpecific + 3215
14 com.apple.CoreFoundation 0x96aaccf8 CFRunLoopRunInMode + 88
15 com.apple.Safari 0x00118d4d 0x1000 + 1146189
16 com.apple.Safari 0x00117fd3 0x1000 + 1142739
17 com.apple.Safari 0x00118081 0x1000 + 1142913
18 libSystem.B.dylib 0x900356f5 _pthread_start + 321
19 libSystem.B.dylib 0x900355b2 thread_start + 34


It does look like a memory issue on the face of it so I swapped the ram with the ram in a MacBook, but the same issue recurred. Running first Tech Tool Pro and then AHD from the system disk found no problems.

So, is this more likely to be the current Safa issues or an actual problem. Since I swapped the RAM over completely I would guess any issues are with the ram slots themeselves rather than the chips.

[GenoG]

Try disabling the new anti-phishing feature. (Preferences > Security > Fraudulent Sites "Warn when visiting a fraudulent website" .

http://discussions.apple.com/thread....6&tstart=0

[TETENAL]

• Remove everything from <home>/Library/InputManagers and /Library/InputManagers
• Update Safari to 3.2.1.

I wouldn't suggest turning off the anti-phishing feature.

[Cold Warrior]

OpenDNS provides robust anti-phishing support in case you really want that feature but not in a web browser.

[DewD]

I downloaded the new Safari 3.2 when it came out, and for the first time ever I had a genuine Apple OS-X app start crashing right and left. The only add-on / plug-in I was using was Pith Helmet, so I removed it. Didn't help. Neither did upgrading to Safari 3.2.1

BUT---there is a new update to PithHelmet...v 2.8.4 ...came out the day before Thanksgiving. It solved my Safari crash issue, and I am reporting that Safari.3.2.x is now much MUCH faster than my default FireFox 3.0.4 ( with AdBlockPlus) and has yet to crash or choke on Flash ; JavaScript, etc. I tested it first on my old eMac 800 before putting it on the two newer G4's. No issues on any of those PPC Macs.

This is interesting: I'm still running Tiger on PowerPC Macs. I read elsewhere that the newer version(s) of PithHelmet are written for Leopard. YMMV.

PithHelmet is at www.culater.net , and yes you should pay the measly $ 10.00 to Mike for this extremely useful plug-in