Safari Crash Assistance Needed
 

I have a Power Mac G4 FW800 with 1.75 gb RAM and all of the latest OS Tiger updates.

I am having a great deal of problems with Safari. Safari is constantly crashing and freezing. I have performed the ordinarily suggested trouble-shooting methods, ie.: repaired permissions, replaced the Safari plist file, reset Safari, Repaired the hard disk using the Tiger DVD.

This problem has become significantly worse since the 10.4.5 update.

I checked the Activity Monitor Application while Safari is running, and it indicates that Safari is running at 90%+ usage while selecting any of the available tabs; CPU, System Memory, Disk Activity, Disk Usage and Network.

Another Safari weirdness is occuring in a window that has several tabs opened. If I click on a tab to select it, a tab several tabs to the right will actually be displayed, not the tab I am clicking on to view.

I am not an expert user, and I do not know where to turn to or how to fix this problem.

Is there anyone who has the expertise to help me resolve this problem?

I would greatly appreciate any and all help.

Thank you very much!

Michael

Does the problem occur when logged in as another user?

Hello,

I created a new test user and the same problems occur in that account also.

I forgot to mention strange issue that presents in Safari.

If I have Safari open and quit another application that is running, the menu bar for the appication that I have quit still appears as if the application is running. I checked the Activity Monitor and the Dock icon, and yes, the application has quit, but the menu for that application remains in the menu bar, and I am unable to return back to Safari, either by selecting the Safari icon in the dock, or by selecting any open Safari window in the dock or open on the desktop.

I also forgot to mention that I have tried reinstalling the 10 . 4.5 update, and this has not affected these issues.

I appreciate your input and advice and hope that this can be resolved.

Michael

1) You should try removing all 3rd-party system "enhancements" (e.g. anything that depends on Unsanity's APE) and Safari extensions or enhancements.
Safari extensions are usually found in either ~/Library/InputManagers or /Library/InputManagers
Since you have the same problems with a new user, look first in /Library/InputManagers (Library folder at the top of the drive).

2) (if you still have problems after removing the above 3rd-party software)
Launch the "Console" application (under /Applications/Utilities) and look for relevant error messages. Note that messages are labeled with the date & time so you can use that to locate the part of the log to look at. Copy & paste the relevant messages back here so we can see them.

If the log refers to a crash log, press the "Logs" button (top-left) and go into the ~/Library/Logs section to find that particular crash log. Copy & paste back here the last portion of that crash log - the part that gives details about the last crash (or preferably attach it as a plain text file, using the "Manage Attachments" button at the bottom when you reply).

Hello Again,

I followed the directions and I also followed all other standard trouble-shooting suggestions, and Safari is still crashing repeatedly.

This is my first attempt at using the Console app, so I apologize if I make a mistake in posting the information requested to help solve this issue.

I look forward to hearing your advice.

Thank you,

Michael

The interesting part:
So the first thing is, have you tried removing Saft (or maybe upgrading it, it could just be out of date) and seeing what happens?

I have already completely removed Saft and all of it's components. Prior to removing Saft for the trouble-shooting procedures, I had the most current version installed. I have no other Safari enhancements installed; only the most currently available version of safari isw installed and running.

Thak you,


Michael

I thought I whould add that I just checked the Activity Monitor and Safari is still using 90%+ of CPU, System Memory, etc..

MIchael

Long shot, but do you connect to the internet via a proxy using a PAC file? In my experience, that makes Safari incredibly unstable (I think it has to do with the fact that Safari grabs a fresh copy of the PAC with every connection it makes, as opposed to once per session). In my case, the solution was to manually configure my system's proxy rather than use the PAC.

Hello Franko,

Thank you for you insight. My connection to the internet is via broadband cable, and I am not using a proxy of any type.

thank you,

Michael

You don't seem to have followed directions about removing items from the two InputManagers folders - see these lines from the latest crash report that you attached:
I note also that the crash seems to have something to do with JavaScript.

Hello Hayne,

Thank you for your time and help. After reading your reply, I checked the InputManagers folders both for ~/Library/InputManagers or /Library/InputManagers, and both folders indicate zero items in the folders. The files I removed are sitting in the trash. My Mac has been restarted many, many times since I removed the items as you directed. Do you have any idea why they may still be showing up in the crash log?

I have no ability to read a Crash Log, and admit ignorance in this area.

Any further help you may suggest is greatly appreciated.

Michael

I have no idea why they would be showing up in the crash log if you have restarted your Mac after moving them to the crash - assuming that the crash report is from after that time.

To be sure, please launch the "Terminal" application (under /Applications/Utilities) and copy & paste the following commands, press Return, then copy & paste the results back here so we can see:

id
ls -la ~/Library/InputManagers
ls -la /Library/InputManagers
echo "done"

And there's no big trick to reading a crash log. You just ignore all the numbers and look at the text. The interesting parts are the thread that crashed and the list of software that is in memory at the time.

Prospect

Join Date: Oct 2004
Posts: 26
Hello Hayne,

Yes, the crash report is from after the time I deleted the InputManager files.

I am attaching the terminal information you requested.

Michael

Well, those results were rather garbled - it looks like you ran the commands, then copied and pasted the results back into the Terminal and then showed us the results of that.
But anyway, reading between the lines, it does look like the two InputManagers folders are empty.

Please restart your Mac (not just log out) and then see what Safari does.
And then attach whatever new crash reports you get.

Have a look in the latest crash reports to see if there are any lines mentioning InputManagers (just search for it - but note that all crash reports are together in the one log file. The latest crash is at the end of the file and that is the one we are interested in)

If you still seem to be getting InputManagers listed in the most recent crash reports, then maybe you need to empty the Trash. I don't understand why this would be necessary if you are indeed restarting the Mac - but anyway ...

The text from the terminal results are directly saved from the terminal window. I didn't copy and paste the information back into the terminal. That was a direct save of the text that Terminal generated. Do these garbled results mean anything?

I will restart my computer, and see what Safari does and then report the results.

Thanks again,

M

It seems hard to believe, but if the Terminal is indeed misbehaving in the manner you showed, then it would indicate some problem.
But I think it more likely that you accidentally pasted the results into the Terminal window, thus executing the results as if they were commands.

Maybe try again if you want to pursue this. Do each step slowly and carefully.
1) Quit Terminal if it is currently running.
2) Launch the Terminal application. You should get a new window that has three lines of text in it: a "Last login" line, a line that says "Welcome to Darwin", and a prompt.
3) Type in the following command and then press Return:
id
4) Copy the full contents of the Terminal window and then start a new reply here and paste what you copied into your reply.

Hello Hayne,

I must tell you, you are a very generous and patient person!

I followed the directions for terminal as asked. Here are the results:

Last login: Sun Feb 26 20:27:50 on console
Welcome to Darwin!
cpe-65-30-182-129:~ michaelnerad$ id
uid=501(michaelnerad) gid=501(michaelnerad) groups=501(michaelnerad), 80(admin)
cpe-65-30-182-129:~ michaelnerad$

I am also sending another reply with a new crash report. At the end of the report ia a line that still has a directory noting "saft bundle". I think it will be much clearer to you if I send a reply with the crash log.

M

Here is the latest craash report from Safari. I found a mention of Saft Bundle near the end of the report. I do not know what this means.

M

I ran the first Terminal command you asked me to process.
This is the text copied and pasted into this message:

Last login: Sun Feb 26 21:43:18 on ttyp1
Welcome to Darwin!
cpe-65-30-182-129:~ michaelnerad$ id
uid=501(michaelnerad) gid=501(michaelnerad) groups=501(michaelnerad), 80(admin)
cpe-65-30-182-129:~ michaelnerad$ ls -la ~/Library/InputManagers
total 16
drwxr-xr-x 3 michaeln michaeln 102 Feb 26 18:57 .
drwx------ 79 michaeln michaeln 2686 Feb 15 12:09 ..
-rw-r--r-- 1 michaeln michaeln 6148 Feb 26 18:57 .DS_Store
cpe-65-30-182-129:~ michaelnerad$ ls -la /Library/InputManagers
total 16
drwxrwxr-x 3 root admin 102 Feb 25 20:40 .
drwxrwxr-t 58 root admin 1972 Dec 23 06:00 ..
-rw-rw-r-- 1 michaeln admin 6148 Feb 25 20:40 .DS_Store
cpe-65-30-182-129:~ michaelnerad$ echo "done"
done
cpe-65-30-182-129:~ michaelnerad$


Is this more helpful?

Michael

The date on that latest crash report seems to be the same date
("Date/Time: 2006-02-25 20:22:58.756 -0600")
as in the previous report you attached. I.e. it is an old report.
So it seems that either you are getting mixed up in what you are attaching, or Safari is not generating any new crash reports.

Try again and pay close attention to the lines in the crash log that start with "Date/Time:"

Much better! I'm not sure what you had done the first time - but whatever...
Anyway, this shows that your two InputManagers folders are indeed effectively empty.