Finder stuck in crash and relaunch loop
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Curious if this has happened to anyone before... when I started my G4, running 10.4.3, this morning, finder launches then immediatley starts flashing off and on, all the icons and menu bar continously appear then dissappear. It looks as though it's stuck in a crash/relaunch loop.
I'm unable to do anything, I can open a window for a split second before it crashes again. I've rebooted from the disc and repaired permissions and the drive, as well as trying to startup without startup items and resetting the PRAM.
Can't think of anything else to fix this problem, so I'm just going to reinstall the OS. I searched the forums here, but didn't see any posts for this problem. Anyone know what's going on?
15 replies
Sign in or join Beachball Help to reply.
- 0
Frank STENGEL ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Wait before reinstalling OSX. There are things one can try before that.
Do you have ony one admin user? Then follow this list. If not skip ahead
- Print this
- Reboot and start in single user mode (command-S on startup)
- Mount the main filesystem by typing the text in the grey box
/sbin/mount -uw /
- I am assuming here that your short name is shortname. continue by typing the text in the grey boxes
cd /Users/shortname
mv Library/Preferences/com.apple.finder.plist Desktop
reboot
If you have more than one admin user then
- Login as another admin user
- If the problem persists then post back
- Open Terminal (found in /Application/Utilities/
- Type the text in the grey box. I am assuming the short name for the account where there is a problem is shortname. You will have to adapt the text accordingly. You might have to type the password of the account you are currently logged in as
sudo mv /Users/shortname/Library/Preferences/com.apple.finder.plist /Users/shortname
beware: the text on the above is on one line...
- Reboot
Message was edited by: Frank STENGEL
- 0
Cacho ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Okay, I'll wait, what can try?
- 0
Frank STENGEL ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Read the rest of the message: I don't type too fast... In case of any doubt, ask!
- 0
Frank STENGEL ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Having doubts: I should have said "read the rest of my first message"...
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, Cacho and Frank —
I'm writing to contribute purely anecdotal support. I otherwise leave you in Frank's very capable hands.
"
Curious if this has happened to anyone before..."
Yes.
Several times, as an ~immediate precursor to failure of my disk directory. In that case, the solution turned out to be replacement of "bad RAM" that had caused the directory damage. Once the RAM was replaced, the directory rebuilt with DiskWarrior, and an Archive & Install completed, everything was fine.
I can imagine another circumstance — though there may be many others. As is described in the Configuring User Sessions subsection of
The Boot Process:"Once the user session is up and running, loginwindow monitors the session and user applications in the following ways:
• It manages the logout, restart, and shutdown procedures...
• It manages the Force Quit window, which includes monitoring the currently active applications and responding to user requests to force-quit applications and relaunch the Finder. (Users open this window from the Apple menu or by pressing Command-Option-Escape.)
• It writes any standard-error (stderr) output to a log file. Log files are stored in the /Library/Logs/Console/<uid>/console.log file, where <uid> is the user ID of the currently logged in user.
If the Finder, Dock, or SystemUIServer processes die for some reason, loginwindow automatically restarts them. In the same manner, if the loginwindow process dies, the launchd process automatically restarts it...."
This implies several mechanisms — not that it helps much...
Btw, please try to post back to iinteract with Frank as frequently as is feasible. Otherwise, participants may worry that you've suffered something similar to my initial comment.
Good luck!
Dean - 0
Mbelang ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I tried this solution but this command line is not even being accepted, nor is the solution through Terminal.
Anyone have any other suggestions?? I really don't want to reinstall OS.
thanks.
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, Mbelang —
I'm inclined to think your situation would receive the visibility and attention it deserves if you'd initiate a new thread. Your situation probably differs from Cacho's in ways that may not be apparent.
I'm not clear whether you're currently able to "control" anything on your TiBook. Some of the ideas below presume you have at least partial use...
(1) Please provide as much specific detail about the behavior and circumstances (before/during) as you can.
If feasible, looking at your user and system logs may provide useful information to help diagnose the problem. Using
Console, you may be able to access
Finder.crash.logs in the
~/Library/Logs/
directory. Alternately, if you can get Activity Monitor to open on your desktop, you may be able to watch the sequence leading up to the Finder crashes.(2) Aside from the Finder, is your TiBook behaving itself? Does it
start up properly? Please consider using the alternate boot methods described in that article to help with troubleshooting. One may enable you to regain some "control" — and allow you to delete Finder preferences, as Frank'ps ost suggested.Do you have access to use/borrow another Mac so that you can utilize
FireWire Target Disk Mode (TDM) to access the Finder
.plist?(3) Have you received any
kernel panic alerts?(4) Have you
C-booted to your Install Disc and run Disk Utility (DU) / Disk First Aid to "repair disk"? Confirming the integrity of your disk directory may prove important. Please note your HD's
S.M.A.R.T. status from the DU window while doing this.(5) Have you run
Apple Hardware Test lately?(6) What else have you tried?
Regards,
DeanI edited this message...
- 0
Mbelang ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
My TiBook just started acting odd over the past couple of days. I've been doing a lot of work with video and I'm not sure if that has something to do with it (I recently degragged).
Last night when I was shutting down, it went into kernel panic. It started back up this morning fine, but then started this continuous closing and launching of Finder.I'm not able to get into console to get crash logs, nor can I open Activity Monitor. I can, however, log into my guest account fine, but don't have access to log file for my user account (or do I?).
I have run permissions repair, disk repair, and hardware test with no problems reported and no success in curing my latest issue. Booting in safe mode doesn't fix the problem either.
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi again, Mbelang —
(7) I'm not clear enough on your situation to say definitively, but you may be able to start up into
Safe or
Single-User Mode as a means to begin troubleshooting your account. If so, you may be able to delete Finder preferences directly, with or without the Terminal commands Frank's post provided — and gain access to the most current and relevant
panic.log information.(8) I think the logged messages may be helpful in troubleshooting what's happening. If you can access them, pasting excerpts here may help folks to help you.
(9) I believe there should be a way to access what you need from another account using Terminal — in order to trash the preferences, anyway —
but must leave that to advice from other participants.
(10) Alternately — might it be feasible for you to use/borrow another Mac so that you could utilize FireWire Target Disk Mode (TDM) to access your HD and the Finder .plist? This may also facilitate saving any data that's not included in your last backup — which I think should be considered a high priority, even though your disk directory seems OK.
(11) Do you have adequate HD space available for your video work, system requirements, etc. Recognizing that optimization ("defragging") may be appropriate if you've such huge files writing to and from disk, that may be complicit in what occurred. Please elaborate on the "defragging."
Regards,
Dean - 0
Mbelang ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can't thank you enough for your help. I fortunately did have another Mac to open up in Target mode with. I retrieved some console logs and found that a Quicktime component was causing the problem:
Mac OS X Version 10.4.3 (Build 8F46)
2005-12-16 10:41:28 -0500
2005-12-16 10:41:28.547 loginwindow[69] FSResolveAliasWithMountFlags returned err = -35
2005-12-16 10:41:28.748 loginwindow[69] FSResolveAliasWithMountFlags returned err = -35
Waiting for MirrorAgent to launch and respond to CFMessagePortCreateRemote(). [199]
2005-12-16 10:41:29.803 HPEventHandler[215]: DebugAssert: Third Party Client: ((__null) != m_lock && 0 == (*__error())) Can't create semaphore lock [/Volumes/Development/HP/Mac-Software/mac-software/core/HPEventHandler/Sources/ HPTMNotificationManager.cpp:60]
Dec 16 10:41:31 marc-belangers-powerbook-g4-15 mDNSResponder: NAT Port Mapping (LLQ event port.): timeout
2005-12-16 10:41:33.509 MainMenu[213] Checking OS version
2005-12-16 10:41:39.104 Finder[199] CFLog (21): Error loading /Users/marcusbelanger/Library/QuickTime/LiveType.component/Contents/MacOS/LiveT ype: error code 4, error number 0 (Library not loaded: /System/Library/PrivateFrameworks/LiveType.framework/Versions/A/LiveType
Referenced from: /Users/marcusbelanger/Library/QuickTime/LiveType.component/Contents/MacOS/LiveT ype
Reason: image not found)
2005-12-16 10:41:39.116 Finder[199] CFLog (21): Error loading /Users/marcusbelanger/Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5: error code 4, error number 0 (Library not loaded: /Library/Application Support/DivXNetworks/liblame3.92.dylib
Referenced from: /Users/marcusbelanger/Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5
Reason: image not found)
2005-12-16 10:41:39.126 Finder[199] CFLog (21): Error loading /Users/marcusbelanger/Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5: error code 4, error number 0 (Library not loaded: /Library/Application Support/DivXNetworks/liblame3.92.dylib
Referenced from: /Users/marcusbelanger/Library/QuickTime/DivX 5.component/Contents/MacOS/DivX 5
Reason: image not found)
...and over and over and over.I wasn't sure how to solve it other than remove my component files from the Quicktime folder and it worked!! Now I'll put them back one at a time, except the DivX5.component.
Thanks again!
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi again, Marc —
You're quite welcome. (Although I'm not sure whether, in the end, I was very much help...)
I'm returning, in part, because of a link from another thread involving a MirrorAgent log message like yours.
Thought I'd share that as a general "heads-up" for your future reference, just in case more than the DivX CODEC (compressor-decompressor) issue is involved in what was plaguing your TiBook. Maybe — maybe not; just thought that — based on your log — you'd want to know...
MirrorAgent factors into iDisk synchronization — and has apparently been complicit in a few issues. In addition to the links that Fumiaki provides ~90% into the thread I linked above, you may want to look at this thread in the Mac OS X Server »» Portable Home Directories forum — &/or search Discussions further...
Best wishes!
Hi, Cacho —
Have you made any progress on the issue that prompted you to initiate this thread? I notice you've posted about RAID setup, but I wonder whether you've resolved this — or would like to discuss it further...
Warm regards,
Dean - 0
Cacho ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
When I initially posted, I needed to use the computer right away, so I spent 1/2 hour and did a clean install. Couple months later computer has been fine, except for this morning I'm getting the same problem again. Which, after reading your last post, leads me to believe it's bad ram. I've had bad ram problems on other macs before.
I'm going to try that single user mode command line tip posted above, see if that works... and also do a hardware test on the ram, see which dimms are bad if that's the case.
- 0
Cacho ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I tried the command line stuff that Frank suggested, I didn't solve the problem, although I'm not sure I entered it correctly, but it seemed to accept what I entered.
If the purpose of the command line stuff is to trash the plist file, then I know I can do that more easily in target disk mode. So I will try that next.
Meanwhile, I did a quick hardware test and the ram checked out fine... doing an extended hardware test now. If it still checks out fine, I might pop the ram in and out, maybe put the 2 dimms I have in different slots.
- 0
Cacho ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Update:
Ran the extended hardware test, RAM passed.
Removed RAM and put into new slots.
Rebooted, same problem.Did target disk mode, trashed finder.plist... Rebooted, same problem.
Did single user startup, entered command line stuff, first line that Frank suggests:
"/sbin/mount -uw /" I get an error, forget what it says.Tried the second lines Frank suggests, which worked earlier this morning when I tried, now it says "no such file or directory" perhaps because I trashed the finder.plist file?
I would've reinstalled the OS by now, but becuase it's the 2nd time to happen since doing a clean install, I'd like to figure out a quicker fix incase it happens again in the future.
- 0
fahlman ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Do you have files on your Desktop? If so boot back in to Target Disk Mode and move all files from your Desktop to your Documents folder.
This exact same thing happened to a user account on one of my computers last week. Finally this morning I was talking to a business acquaintance of mine who suggested exactly what I have suggested above. It worked perfectly. Let us know if it works.