Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A fix for a rapidly and repeatedly crashing Finder' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A fix for a rapidly and repeatedly crashing Finder
Authored by: donaciano on Jun 29, '04 12:16:35PM

I actually had this same problem 2 weeks ago, but I managed to narrow down the cause a little bit more. My corrupted file was not on the desktop but in a subfolder far enough down in columns view that it had to be scrolled down to be seen. If the finder window was scrolled to where it would begin to show it would immediately crash the Finder which would restart. Fortunately the window position would be reset to the top of the column and I could do it again if I wanted or not. ;-) Copying the file via command-line resulted in a Resource-less copy of it which worked fine once it was given the right extension. I believe copying the Resource-less file over the original did NOT fix it, the cp command can't erase or change any resc I believe. The only way to fix it was either to delete the file vi command-line and then move the resc-free one back where it was, or to create a completely new folder and after moving the clean version of the file over I was able to use the FInder to move the rest.

I did at one point turn the folder view into Icons at which point I had a rebooting finder like the original hint mentioned. Not sure how I got out of that one, but it was annoying. :-)

I wish I had more experience with Mac resource forks but I'm an OS X switcher so a bit lacking in that dept, plus I needed the file and couldn't really play around with it. OH! The reason I noticed the corrupted file in the first place is that CCC complained that it couldn't be copied. That's what alerted me.

Panther on an iBook 640MB, 10.3.4 up to date.
-Don.



[ Reply to This | # ]
A fix for a rapidly and repeatedly crashing Finder
Authored by: drubert on Jul 03, '04 01:27:55AM

Thank you for posting - I've been searching everywhere and not finding much.
Unfortunately - the posted solutions are not helping me much.

Here is what I have done.
I have a second machine that I can use to connect to my mucked up machine.
I've removed all files from the desktop.
I had ton's of stuff in the .trash --- I deleted all those.
I booted in single user and ran fsck.
This did show two messages that were similar just with different file#s.
Overlapped extent allocation (file 299234d)
I have no idea what that means - or if it is related.

Here is what is common. (perhaps to find the cause)
I recently did move a large # of files onto the desktop (mame ROMS)

I'm still down!
Any other ideas?



[ Reply to This | # ]