10.3.9 and Safari

>Has anyone else had Safari start crashing on them regularly since updating
>to 10.3.9?

Is it related to Java? Today Apple acknowledged a problem with
10.3.9 and Java well, breaking.
        http://docs.info.apple.com/article.html?artnum=301380

The solution basically amounts to re-installing either the Java 1.4.2
Update 2 or Security 2005-002 updates.

Oh, and beware of the Server 10.3.9 update. On a machine here it
rewrote a key line in one of OpenLDAP's slapd.conf files, in doing so
rendering inoperable shared home directories.

--
Andrew Laurence
atlaurenuci.edu

> Has anyone else had Safari start crashing on them regularly since
> updating
> to 10.3.9? For me it's gone from pretty much rock-solid to randomly
> fall
> over without warning.

I had a problem where Safari 1.3 would crash without fail whenever I
tried accessing my Bookmarks or History. After trying everything else I
could think of, I downloaded the full updater and used Pacifist to
reinstall just Safari 1.3 -- and now it works great.


[I've heard that various old Safari plug-ins can cause major problems with the latest version of Safari. -Adam]


BRIAN/bpearcecloud9.net
<http://www.redjacketpress.com>
"Yesterday's Books for Today's Reader"

On 20/4/2005 1:33 PM, "Andrew Laurence" <atlaurenes.nacs.uci.edu> spake
thus:

> Is it related to Java?

Very unlikely. All other Java related things work fine (including Apple's
test to see whether the problem exists), and I wasn't accessing anything
involving Java at any point when Safari crashed. If all else fails I'll try
reapplying the security update.

I'm working on some of the MacFixit suggestions at the moment, but the
University's network has thrown one of it's all-too-common go-slow fits and
I'm currently downloading at 1KB/s :(

--
Nigel Stanger, Dunedin, NEW ZEALAND.
http://public.xdi.org/=nigel.stanger

>Has anyone else had Safari start crashing on them regularly since updating
>to 10.3.9?

MacOSXHints reports crashes caused by third-party add-ons like Saft
and AcidSearch, and recommends disabling them or updating to latest
editions:

<http://www.macosxhints.com/article.php?story=20050418070304105>

No crashes yet for my part, but I've already reported two apparent
new bugs to Apple:

1. Can't turn off 'Google Search' by means of 'View->Show->Google
Search' -- there's no tick beside it in the menu, the plist says
'false', but it's still there in the Address Bar!

2. Printing some pages produces an extra blank page at the end where
previously they printed okay (still trying to find a pattern to this).

Chris Reed, BBR Solutions Ltd * http://www.bbr-online.com

On 4/19/2005 18:29, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz>
wrote:

Aside from the Java problem--easy to test, see below--you need to update
oddities (or essentials, depending on point of view) like Pith Helmet, Saft
(if that's the right spelling) etc. Most are broken...this is a significant
update to Safari, per one of the developers, making it as much like the
Tiger version as possible given the different lower-level stuff.

A range of solutions has been discussed at MacFixIt and elsewhere...an easy
one which works for many people is to reapply the 10.3.9 update using the
combo updater. Apple has endorsed reapplying the most recent pre-10.3.9
update if Java is broken.

So...is Java broken on your machine? Go to terminal, and type

java -version

You should see something like
$java -version
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-141.4)
Java HotSpot(TM) Client VM (build 1.4.2-38, mixed mode)

If you see a failure instead, you have the Java problem. Otherwise, you
likely have the stale Pith Helmet (et al) problem.

By the way, Firefox takes a more draconian approach to extensions...updates
of significance to the way extensions work disable all the extensions. Not
a bad idea.

  --John (sending also to Nigel in case the moderators use someone else's
response instead)

I use two addons to Safari, AcidSearch and PithHelmet. AcidSearch would
crash Safari 1.3 at startup, period. PithHelmet disabled itself. The
new version of Acidsearch is just fine, while PithHelmet 2.3.1 (while
not disabling itself) would make Safari crash every once in a while
(due to an issue with collapsing images)--PithHelmet 2.4 works around
the problems and I've had no problems since then.

Apparently the core of the new Safari is very similar to Tiger's
Safari, so hopefully once everything works for 10.3.9 it should work in
Tiger without too much tweaking.

macmaxbh

"Chris Reed, BBR" <c.s.reedbbr-online.com> wrote:

>2. Printing some pages produces an extra blank page at the end where
>previously they printed okay (still trying to find a pattern to this).

I wonder if this problem with Safari may explain why my Epson printed also
just started to produce blank pages. The trouble with that hypothesis in my
case is that the blank pages were produced when I was printing from a Word
document! Could the bug have jumped from one app to another? Sounds like a
Mac variant on Avian Flu!

Paul

Deleting your Safari caches can be helpful in making the transition
to Safari 1.3 stable.

Craig Sutherland

On 21 Apr 2005, at 11:25 :32, macmaxbh wrote:
> Apparently the core of the new Safari is very similar to Tiger's
> Safari, so hopefully once everything works for 10.3.9 it should
> work in
> Tiger without too much tweaking.

I believe the core (that is, WebCore) is not very similar, but
exactly the same. WebKit and the Safari app itself are not the same
as Tiger's, but I think the WebCore portion is.

On 21/4/2005 2:42 AM, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz>
spake thus:

> I'm working on some of the MacFixit suggestions at the moment, but the
> University's network has thrown one of it's all-too-common go-slow fits and
> I'm currently downloading at 1KB/s :(

OK, now I'm starting to get worried. Not only have I (a) tried most of the
suggested solutions without any success, but (b) FireFox and Camino now seem
to be exhibiting similar falling-over behaviour :( (although not as
frequently as Safari; I haven't tried Mozilla)

What I've done so far (with no effect):

1. Check Java (OK)
2. Delete all caches (no effect)
3. Reinstall Safari 1.3 using Pacifist (no effect)
4. Repair permissions (no effect)
5. Delete com.apple.Safari.plist (seemed to work for a while, but no)
6. Remove all SIMBL plugins (only growl, no effect)

I haven't tried reinstalling Security Update 2005-003 or the entire 10.3.9
combo update yet. I think my next (and possibly final?) attempt will be:

* Delete com.apple.Safari.plist
* Repair permissions
* Delete all caches
* Reinstall 10.3.9 Combo Update
* Repair permissions again

Any other suggestions?

--
Nigel Stanger, Dunedin, NEW ZEALAND.
http://public.xdi.org/=nigel.stanger

On 4/22/2005 7:51, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz> wrote:

> * Delete com.apple.Safari.plist
> * Repair permissions
> * Delete all caches
> * Reinstall 10.3.9 Combo Update
> * Repair permissions again
>
> Any other suggestions?

This not only leads to the software update Apple issued yesterday, but
contains a cogent explanation of what goes wrong and what the update does.
It's probably time to stop applying fixes and install the update instead.

<http://docs.info.apple.com/article.html?artnum=301382>

Headline is
About the Java Update for Mac OS X v10.3.9

  --John

On 23/4/2005 3:50 AM, "John W. Baxter" <jwblistolympus.net> spake thus:

> About the Java Update for Mac OS X v10.3.9

Tried that, and it doesn't seem to have helped, which isn't surprising given
that I don't think Java was the problem anyway :(

--
Nigel Stanger, <http://www.business.otago.ac.nz/infosci/>
Dept. of Information Science, <http://public.xdi.org/=nigel.stanger>
University of Otago, Dunedin, NEW ZEALAND. +64-3-479-8179

Yes, I have had several, to many instances where Safari "Unexpectedly
Quits" without warning. It appears to happen when introducing a
graphics program or operating within a graphics program. Perhaps too
much load ???? This began shortly after downloading and installing
10.3.9. Safari can be re-initialized quickly and seldom crashes after
that---strange !!! Bruce Harlan

My problem with the update involves my external firewire hard drive (sorry for going off-topic). This is a story we've all heard before. I wasn't affected before, and this time didn't expect any problems (doh!).

Fortunately it's a Macally enclosure, and they were very responsive. Their firmware update installer was programmed by a very intelligent person (although it's not posted on their website), and I didn't lose any data. I first discovered this solution at:

http://forums.macrumors.com/showthread.php?p=1390390&mode=linear (scroll down to post number 17)

Other users also posted their problems with Safari after the install. As for me, I didn't install the java update and am having no Safari problems yet. I'm not going to install it for a few weeks until Apple has time to get some of the kinks out.

I kick myself for installing the 10.3.9 update without waiting longer and investigating for problems.

Sincerely, Ted Shaw

Bruce Harlan said:

>Yes, I have had several, to many instances where Safari "Unexpectedly
>Quits" without warning. It appears to happen when introducing a
>graphics program or operating within a graphics program. Perhaps too
>much load ???? This began shortly after downloading and installing
>10.3.9. Safari can be re-initialized quickly and seldom crashes after
>that---strange !!!

This isn't an uncommon problem.

See:
How To Deal With Common OS X 10.3 Panther Problems
http://www.macattorney.com/panther.html
Item #25

Also give Preferential Treatment (free) a try.
http://homepage.mac.com/jonn8/as/html/pt.html

PT doesn't always find every corrupted preferences file, but since it is
fast, free, and easy to use, it is worth a try to see if it finds
anything.

Another thing to try, if none of the above helps, is manually
uninstalling the invisible user file:
" .GlobalPreferences.plist"
which is located at:

Users/[User Name]/Library/Preferences/.GlobalPreferences.plist

Don't get this file confused with the file of the exact same name located
at:
/Library/Preferences/.GlobalPreferences.plist




Randy B. Singer
Co-Author of: The Macintosh Bible (4th, 5th and 6th editions)

Routine OS X Maintenance and Generic Troubleshooting
http://www.macattorney.com/ts.html

On 23/4/2005 2:51 AM, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz>
spake thus:

> * Delete com.apple.Safari.plist
> * Repair permissions
> * Delete all caches
> * Reinstall 10.3.9 Combo Update
> * Repair permissions again

I think I may have cracked it! The above didn't work :( but I had at least
figured out that Safari seemed to be commonly crashing just after clicking
the close widget on either a window or a tab (intermittently, of course).

While scratching my head I decided to have a look at the Safari crash log,
and discovered something very interesting in the "Binary Images Description"
section, where it tells you what all was loaded at the time of the crash:


  0x430000 - 0x431fff com.presenta.iGetterIMBundle 2.0
/Users/nstanger/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle
/Contents/MacOS/iGetterIMBundle
  0x43a000 - 0x43bfff com.presenta.iGetterSafariBundle 2.0
/Users/nstanger/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle
/Contents/Resources/iGetterSafariBundle.bundle/Contents/MacOS/iGetterSafariB
undle
  0x443000 - 0x443fff com.aladdinsys.mmenabler 7.0
/Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/Mac
OS/MagicMenuEnabler
  0x454000 - 0x455fff net.culater.SIMBL 0.2 (6)
/Library/InputManagers/SIMBL/SIMBL.bundle/Contents/MacOS/SIMBL


iGetter hasn't been installed on my machine for some time, and I thought I'd
removed all the SIMBL stuff (I think it was installed by Growl). Obviously
not. (MagicMenu is pretty much irrelevant, I think.) Anyway, I trashed the
iGetter and SIMBL stuff, and Safari so far appears to be behaving (fingers
crossed). It also feels a bit snappier than before too.

Here's hoping!

--
Nigel Stanger, <http://www.business.otago.ac.nz/infosci/>
Dept. of Information Science, <http://public.xdi.org/=nigel.stanger>
University of Otago, Dunedin, NEW ZEALAND. +64-3-479-8179

On 4/26/2005 23:14, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz>
wrote:

> iGetter hasn't been installed on my machine for some time, and I thought I'd
> removed all the SIMBL stuff (I think it was installed by Growl). Obviously
> not. (MagicMenu is pretty much irrelevant, I think.) Anyway, I trashed the
> iGetter and SIMBL stuff, and Safari so far appears to be behaving (fingers
> crossed). It also feels a bit snappier than before too.

MagicMenu is probably irrelevant. With the current Stuffit Deluxe, I as
usual told the installer not to install Magic Menu (which after bad
experiences early on I've never trusted, plus it's an unneeded third party
gadget). So far, MM seems to be doing no harm.

  --John

At 10:15 -0700 28/4/05, John W. Baxter wrote:
>On 4/26/2005 23:14, "Nigel Stanger" <nstangerinfoscience.otago.ac.nz>
>wrote:
>
>> iGetter hasn't been installed on my machine for some time, and I thought I'd
>> removed all the SIMBL stuff (I think it was installed by Growl). Obviously
>> not. (MagicMenu is pretty much irrelevant, I think.) Anyway, I trashed the
>> iGetter and SIMBL stuff, and Safari so far appears to be behaving (fingers
>> crossed). It also feels a bit snappier than before too.
>
>MagicMenu is probably irrelevant. With the current Stuffit Deluxe, I as
>usual told the installer not to install Magic Menu (which after bad
>experiences early on I've never trusted, plus it's an unneeded third party
>gadget). So far, MM seems to be doing no harm.
>
> --John

I don't know about MM, but one thing this updater did was kill the
relationship between Safari and URLmanager. Now when I hit Cmd-D when
in Safari, URLManager won't launch as it used to do......

~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Hinckley, Gingins, Switzerland
home: dbhsuiattle.org
work: dahhq.iucn.org; http://iucn.org/
the Suiattle: 48º 19' N, 121º 32' W
Gingins: 46° 24.685 N, 6° 10.556 E