Welcome to the MacNN Forums.

MacMan4000 · 05:51 PM

After I installed the combo update via software update last night Safari has been on the blink. (and much faster, but thats beside the point). In all of the following situations Safari does an "unexpected quit"

close a window
close a tab
press command+w
press command+q
choose file>quit
random moments

All of these are 100% replicate-able, except the random moments one.

Anyone else having problems? anyone know how to fix it?

I already re-downloaded the combo update and tried re-installing. That had no effect. I have never used anything like Acid-search, or any plugins at all for that matter.

Im stumped

Thorin · Apr 16, 2005, 05:03 PM

Is it the java problem? Open Terminal, type "java -version" what does it say?

If it says "segmentation fault" or something similar, rather than telling you the version of java on your machine, then you've got the Java problem the 10.3.9 update's caused. Best way to fix it seems to be to download the 2005-002 Security Update and install it. You can get it here:

http://www.apple.com/support/downloa...34orlater.html

TETENAL · Apr 16, 2005, 05:25 PM

iGetter

MacMan4000 · Apr 16, 2005, 05:49 PM

It WAS iGetter! Wow, that was too easy... i was prepared for the worst. Thanks TETENAL!
Thorin, thanks for the suggestion. I did what you said and I got a version number, not an error. So that appears to be fine.

Thanks again.

alphasubzero949 · Apr 16, 2005, 05:51 PM

Originally Posted by Thorin

Is it the java problem? Open Terminal, type "java -version" what does it say?

If it says "segmentation fault" or something similar, rather than telling you the version of java on your machine, then you've got the Java problem the 10.3.9 update's caused. Best way to fix it seems to be to download the 2005-002 Security Update and install it. You can get it here:

http://www.apple.com/support/downloa...34orlater.html

Awesome...had the same problem here.

What the hell has been going on with Apple's QA these days with Panther?

Thinine · Apr 16, 2005, 06:14 PM

Apple doesn't support 3rd party hacks in Safari, so the fact that they cause crashes is irrelevant. Apple is not responsible for the crap you put in the machine. You'll notice that Safari works perfectly when you remove the haxies.

Big Mac · Apr 16, 2005, 06:18 PM

Thinine: alphasubzero was referring to the security update, not a haxie. Is it simply the case that people who have not downloaded the security update are having the problem, and they just need to get the update to fix it?

Thinine · Apr 16, 2005, 06:24 PM

The Java problem shouldn't have caused crashes, just Java problems. And find out what caused the problem in the first place before you blame Apple.

Mediaman_12 · Apr 16, 2005, 06:29 PM

On a slight tangent, It seams to be 'beachballing' a lot mote than the old one did. For example if I click a link in one tab, then switch tabs to view a different page, I get a Beachball until the page in the 'non-active' tab has loaded, makes tabs mostly pointless.

alphasubzero949 · Apr 16, 2005, 08:35 PM

Originally Posted by Thinine

The Java problem shouldn't have caused crashes, just Java problems. And find out what caused the problem in the first place before you blame Apple.

Don't be such an Apple fanboy.

I properly downloaded and installed Security Update #2 a while back, then installed the delta update through software update last night, which effectively broke Java. I had to go back and re-apply Security Update #2 just to get it working again. So yes, that is Apple's problem that they cannot get their software to update correctly.

Just because things are working smoothly for you doesn't mean that it's automatically the user's fault when system-installed software breaks following an update.

schuey100 · Apr 16, 2005, 09:22 PM

Originally Posted by Thinine

Apple doesn't support 3rd party hacks in Safari, so the fact that they cause crashes is irrelevant. Apple is not responsible for the crap you put in the machine. You'll notice that Safari works perfectly when you remove the haxies.

Actually that's not true at all. Safari is dog slow and people experience endless beachballs when autofill of passwords and address books is on. It's ridiculous.

alphasubzero949 · Apr 16, 2005, 09:50 PM

Good to see that I'm not the only one who had Java break after applying 10.3.9. That's okay; it must be the fault of the users for downloading this update and not Apple.

To find out if Java is broken, open the Terminal and type java -version

If you get "segmentation fault," it's broken.

As in my case, reapplying Security Update 2005-002 fixes the problem.

jay3ld · Apr 17, 2005, 12:50 AM

i had problems with my safari till i removed SIMBL

is there going 2 be an update for these 3rd party hacks like SIMBL so they will work again?

alphasubzero949 · Apr 17, 2005, 01:51 AM

Originally Posted by jay3ld

i had problems with my safari till i removed SIMBL

is there going 2 be an update for these 3rd party hacks like SIMBL so they will work again?

PithHelmet 2.3 is out, but it basically fixed a value in the info.plist file within the PithHelmet.bundle package. Changing the value of "MaxBundleVersion" to the current version of Safari has worked in the past when newer Safari updates broke PithHelmet.

jasonjac123 · Apr 17, 2005, 04:12 AM

Originally Posted by Thorin

Is it the java problem? Open Terminal, type "java -version" what does it say?

If it says "segmentation fault" or something similar, rather than telling you the version of java on your machine, then you've got the Java problem the 10.3.9 update's caused. Best way to fix it seems to be to download the 2005-002 Security Update and install it. You can get it here:

http://www.apple.com/support/downloa...34orlater.html

thank ya, thank ya, thank ya. I have spent hours trying to figure out why everything has been so slow on a site with java script. I tried re-installing java, erasing java, un-and installing safari again, clearing cache, not using cache. all the stupid recomentations - but why no one has recomeded running this update again - I don't know. I had prety much given up and just moved to a faster computer to speed things up a little. Now everying is screaming fast. thanks

Thorin · Apr 17, 2005, 05:42 AM

Originally Posted by alphasubzero949

Don't be such an Apple fanboy.

I properly downloaded and installed Security Update #2 a while back, then installed the delta update through software update last night, which effectively broke Java. I had to go back and re-apply Security Update #2 just to get it working again. So yes, that is Apple's problem that they cannot get their software to update correctly.

Just because things are working smoothly for you doesn't mean that it's automatically the user's fault when system-installed software breaks following an update.

It would almost seem to be random as to who is affected by this. My housemate and I are both running very similar set ups, I had the Java problem and he didn't.

desertmac · Apr 17, 2005, 10:13 AM

Anyone figure out how to get Google Maps to work in this version of Safari? I don't have the Java problem (checked in terminal). I have removed PithHelmet (even the newest version), and I have cleaned the caches, etc. Still no luck with Google Maps. The Map shows, but the information in the right hand pane is collapsed. Google Maps works fine under FireFox. Any thoughts?

Targon · Apr 17, 2005, 10:48 AM

Crashing here alot as well. Java and Plugins always disabled latest version of Pithelmet.

Safari seems terribly slow now. Feels laggy and scrolling is now sluggish.

At least we dont have to option click in the downloads window now see the dl rate.

Im going back to 10.3.8

Goldfinger · Apr 17, 2005, 10:52 AM

Originally Posted by jasonjac123

thank ya, thank ya, thank ya. I have spent hours trying to figure out why everything has been so slow on a site with java script. I tried re-installing java, erasing java, un-and installing safari again, clearing cache, not using cache. all the stupid recomentations - but why no one has recomeded running this update again - I don't know. I had prety much given up and just moved to a faster computer to speed things up a little. Now everying is screaming fast. thanks

Java Script has exactly nothing to do with Java, it's just a case of bad naming by Netscape (they invented Java Script IIRC).

Person Man · Apr 17, 2005, 12:11 PM

Originally Posted by desertmac

Anyone figure out how to get Google Maps to work in this version of Safari? I don't have the Java problem (checked in terminal). I have removed PithHelmet (even the newest version), and I have cleaned the caches, etc. Still no luck with Google Maps. The Map shows, but the information in the right hand pane is collapsed. Google Maps works fine under FireFox. Any thoughts?

Enable the Debug menu if you haven't already.

Choose Debug > User Agent > Windows MSIE 6.0 and it will display normally.

My guess is that Safari 1.2 and earlier had a bug in the rendering engine that Google had to work around. Google will fix it for Safari 1.3 users soon enough, but until then, use the workaround provided above.

desertmac · Apr 17, 2005, 12:21 PM

Originally Posted by Person Man

Enable the Debug menu if you haven't already.

Choose Debug > User Agent > Windows MSIE 6.0 and it will display normally.

My guess is that Safari 1.2 and earlier had a bug in the rendering engine that Google had to work around. Google will fix it for Safari 1.3 users soon enough, but until then, use the workaround provided above.

Thanks. Will do.

monkeybrain · Apr 17, 2005, 04:55 PM

Is anyone else having unusual command-clicking to open a link in a new tab behaviour? I have command-click set to my mouse wheel, but it doesn't work. Manually command-clicking doesn't either. However, command-double clicking does open the link. What's up? (using USB overdrive too, and everything works fine in Camino for command-clicking.

Millennium · Apr 18, 2005, 04:53 AM

I haven't had any crashes, but I did notice that the text in the status bar was upside-down. This is not an encouraging sign, as far as Safari 1.3's QA goes.

moodymonster · Apr 18, 2005, 04:58 AM

Originally Posted by Millennium

I haven't had any crashes, but I did notice that the text in the status bar was upside-down. This is not an encouraging sign, as far as Safari 1.3's QA goes.

wtf

Millennium · Apr 18, 2005, 06:17 AM

Originally Posted by moodymonster

wtf

I'm serious. I'll post a screenshot later. The baseline is the same as always, but the text appears underneath it, not over it, and it's upside-down. The statusbar is narrow enough that the tops (bottoms?) of the characters are cut off.

Of course, Safari doesn't display the statusbar by default anyway, so the point will be moot for many users. This is a shame, though; the statusbar is a good first line of defense against malicious links. They really should turn it on by default, once they've got this fixed.