Text Size

New features in Safari 3.2 causing crashes?

updated 01:30 pm EST, Mon November 17, 2008

Safari 3.2 causing crashes

Apple's Safari 3.2 release may be causing more problems than are solved for some users, anecdotes indicate. The browser is said to be crashing frequently in some cases, with at least some incidents being preceded by the "beachball" loading icon. It is unknown why the errors might be occurring, but it is thought that they may be connected to Apple's new anti-phishing safeguards, or alternately, the third-party PithHelmet ad-blocking extension.

Safari 3.2 contains a new version of the WebKit engine, which has been altered to limit the URL types that can be launched through the plug-in interface. WebKit has also been tweaked to run extra validation on JavaScript array indices, and perform better garbage collection. The majority of security updates in the browser are explicitly targeted at Windows XP and Vista users, however, such as remedies to JPEG and TIFF exploits, and other vulnerabilities in components like CoreGraphics and zlib. Aside from anti-phishing protection, the lone Mac security fix solves a problem in which disabling auto-completion would still leave data in Safari's page cache.

 
Previous Comments

PithHelmet

11/17, 01:43pm reply

I was getting constant crashes until I disabled PithHelmet. People should always disable their third party plugins (especially InputManagers) before blaming Apple.

Turias

Mac Elite

Joined: Nov 2003

+4

Me too

11/17, 01:48pm reply

Victim here too. Inquisitor is the only "extra" I have installed, and the day 3.2 dropped it crashed; then crashed again, giving me a spinning beach ball leaving my work Mac mini unusable (couldn't even bring up the force quit window); third time it froze Safari, but after about 10 minutes, I was able to force quit.

This was last Friday; so far, so good today (Monday)...may have to uninstall Inquisitor, though I hear it's a PITA.

Bearsfan34

Junior Member

Joined: Dec 2007

+3

crash

11/17, 02:04pm reply

I had PithHelmet installed, though not activated, and Safari was crashing every time I opened a link in a new tab. After trashing Pith Helmet, everything is fine (trashed the SIMBL folder in Library/Input Managers. No big deal for me, as I use SafariBlock now anyway.

PithHelmet always messes up when there's a Safari update.

elroth

Fresh-Faced Recruit

Joined: Jul 2006

+3

AcidSearch

11/17, 02:16pm reply

I was on the phone with Apple support for almost 2 hours with the Safari 3.2 crash problem. My problem was solved when AcidSearch was deleted.

JeffChrz

Fresh-Faced Recruit

Joined: Feb 2001

+2

No add-ons,

11/17, 02:39pm reply

no problems on the 2 machines I've installed on.

Flying Meat

Fresh-Faced Recruit

Joined: Jan 2007

+3

Glims

11/17, 02:58pm (1 reply) reply

Haven't had any crashes either. I do use Glims, but both machines have been fine.

2006 Intel iMac 1.86
2005 G4 iBook 1.3

Guest

Fresh-Faced Recruit

Joined: Nov 1999

+3

only probs with plugins

11/17, 03:12pm reply

No problems here. I don't use plugins other than 1Password.

Le Flaneur

Dedicated MacNNer

Joined: Oct 1999

+2

No problems!

11/17, 03:21pm reply

Absolutely no problems so far, even with Inquisitor and AdBlock installed.

ricardogf

Fresh-Faced Recruit

Joined: Jan 2003

+3

no problems here in

11/17, 03:22pm reply

in fact certain situations that would routinely cause crashes for me no longer do.

Guest

Fresh-Faced Recruit

Joined: Nov 1999

+2

Flash

11/17, 03:40pm reply

My Safari 3.2 crashes have all been in a Flash thread. Haven't seen an update from Adobe yet.

resuna

Fresh-Faced Recruit

Joined: Jan 2005

+2

Popular News