I upgraded to Snow Leopard yesterday, and I'm having a lot of troubles, Finde, Time Machine and Disk Utility being the most annoying of them. I don't really know which one of them is making the others unstable / crash but well that's starting to be very irritating, now when I try to start the Finder I get this :
*The application Finder.app can't be opened.*
-10810
Restarting the Computer ( Mac Book Pro Uni ) usually fix that, but it's the second time that it's crashing a 220 go files package copy. I ended up doing it with rsync, the copy is still going on ( it will take a long time ) but I'm left with a Zombie Computer where I can't open a finder, and every Application that use it to open some file is crashing itself.
Is there a way to manually relaunch it ( I don't want to reboot, my computer is stuck backing up a lot of files ) ? I tried Sudo Launch the Finder from /System/Library/CoreServices/Finder.app/Contents/MacOS with no luck, any help would be appreciated.
Installed 10.6.3 via software update. Re-enabled spotlight indexing on just my internal drive. 4 minutes later, an mdworker process died and took coreservicesd with it. coreservicesd failed to start with correct version information, after which nothing much works and the Finder spits out a -10180 error.
In other words - nothing has changed, at least for my failure scenario. Perhaps for some of you there is still hope. If you still have hope, cherish it.
I'm testing the various application launchers available, since that's all I used spotlight for anyway. Perhaps when seeds of 10.6.4 start making their way around I'll start to care again.
It appears we share the same bug. I re-enabled Spotlight and it crashed within seconds.
It also appears that the bug is generally worse as my machine will not crash with the very same problem with spotlight disabled within about 10 minutes.
I'm not running any antivirus. I actually haven't triggered this bug for a long time, hopefully 10.6.3 fixed it in my case - I was only having trouble when connecting to SMB shares.
RadioSnow wrote:
I was only having trouble when connecting to SMB shares.
That was my failure case, too. Sorry for the false hope for you spotlighters.
I could generally trigger the issue with a minute or two of continuous browsing through folders on the SMB drive... but I haven't managed to hang the Finder since the update.
Update from a sufferer whose onset is definitely caused by Spotlight indexing:
I made the upgrade to 10.6.3. No other further attempts at a fix, or any particular changes to my system. Just the upgrade.
And surprise: Whereas previously turning on Spotlight indexing would bring on disaster within a minute or two, I've now had indexing running for hours under 10.6.3. So far, no problems! No Finder errors, no weirdness with Dock or menu bar, no keyboard death, nothing odd at all.
Indexing is looking to be painfully slow. Hours ago it said 79 hours remaining; now it says 78. Sometimes it goes down more, then back up to 79. Well, I expect a long indexing process, as it's being recreated from scratch; the important thing is that the bad stuff isn't happening.
So far, that is. I'll post an update again later. In the meantime, let me offer hope that 10.6.3
might be a fix for
some users.
Looks like I'm having the same issue as a lot of people here (or something very similar).
It started a few days ago all of a sudden. I'm not entirely sure what caused it to start happening, but here are the symptoms:
- login sometimes fails (looks like it's logging in, but goes back to user choice screen)
- Finder stops responding, or disappears completely
- attempts to restart Finder get the dreaded -10180 error
- cmd+tab stops working or some apps missing
- force quit window doesn't show all working apps
- can drag app windows round, but they'll stop accepting keyboard input
- menu bar gets screwed up or shows the wrong app
- dock won't launch apps, but the apps folder keeps working (though it's not possible to launch stuff from it)
- once the symptoms start appearing it rapidly gets worst till it's not even possible to logout
- at some point a hard reboot becomes necessary
- an install of 10.6.3 since hasn't fixed it
- using onyx to delete cache files hasn't fixed it
- I tried deleting the user's dock and finder plist files which I thought helped but it came back (or it was just a coincidence)
I don't have any external drives plugged in or USB keys in when it goes wrong. I have a couple of network mounts (via NFS to a QNAP TS-219 NAS drive). The only other things connected to the iMac (Quad Core i7 27inch) are the standard keyboard and mouse (both bluetooth) and a ethernet cable to my router. None of this has changed recently.
In the system logs I get hundreds of these messages:
30/03/2010 20:56:56 com.apple.coreservicesd[180]
* process 180 exceeded 500 log message per second limit - remaining messages this second discarded
* 30/03/2010 20:56:56 com.apple.ReportCrash.Root[179] 2010-03-30 20:56:56.833 ReportCrash[179:2b03] Saved crash report for coreservicesd[180] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd
2010-03-30-205656localhost.crash
30/03/2010 20:56:57 com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 7 seconds
30/03/2010 20:57:36 com.apple.launchd.peruser.501[203] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
30/03/2010 20:57:36 com.apple.launchd[1] (com.apple.metadata.mds[30]) Job appears to have crashed: Segmentation fault
30/03/2010 20:57:36 com.apple.ReportCrash.Root[179] 2010-03-30 20:57:36.748 ReportCrash[179:3a1f] Saved crash report for mds[30] version ??? (???) to /Library/Logs/DiagnosticReports/mds
2010-03-30-205736localhost.crash
30/03/2010 20:57:41 com.apple.launchd[1] (com.apple.loginwindow[32]) Job appears to have crashed: Segmentation fault
30/03/2010 20:57:42 com.apple.ReportCrash.Root[179] 2010-03-30 20:57:42.846 ReportCrash[179:411b] Saved crash report for loginwindow[32] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow
2010-03-30-205742localhost.crash
30/03/2010 20:57:46 com.apple.WindowServer[210] Tue Mar 30 20:57:46 Flexo.local WindowServer[210] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
So it looks like coreservicesd is at fault but I'm not sure how or why. I'll try to reply to this with the crash report - perhaps it'll give someone here an idea of what went wrong. I can see a seg fault, possibly caused by a faulty pointer while trying to resolve a file system path.
I'm about to reinstall 10.6.3 from the combo update and see if that helps.
Apologies for replying to my own posts, but I've just done a reinstall of 10.6.3 from the full combo update. While it was installing that the symptoms reappeared and it wasn't able to restart after the install. Finder and all apps hung and the menu bar disappearred. So, I left it 10 minutes or so till the hard drive activity stopped, then did a hard reboot.
After that it seemed fine for 5 minutes, but I've just seen the errors reappear in the logs.
Here's a list of the crash logs for today (using 'ls -ltr /Library/Logs/DiagnosticReports'):
-rw-rw----@ 1 root admin 10103 30 Mar 07:34 coreservicesd
2010-03-30-073440localhost.crash
-rw-rw----@ 1 root admin 9763 30 Mar 07:34 coreservicesd
2010-03-30-073445localhost.crash
-rw-rw----@ 1 root admin 9116 30 Mar 07:36 lsregister
2010-03-30-073626localhost.crash
-rw-rw----@ 1 root admin 16433 30 Mar 08:53 mdworker
2010-03-30-085315localhost.crash
-rw-rw----@ 1 root admin 10133 30 Mar 08:53 coreservicesd
2010-03-30-085317localhost.crash
-rw-rw----@ 1 root admin 12288 30 Mar 08:54 mds
2010-03-30-085407localhost.crash
-rw-rw----@ 1 root admin 27947 30 Mar 08:54 loginwindow
2010-03-30-085411localhost.crash
-rw-rw----@ 1 root admin 16192 30 Mar 08:57 mdworker
2010-03-30-085757localhost.crash
-rw-rw----@ 1 root admin 9138 30 Mar 08:57 lsregister
2010-03-30-085757localhost.crash
-rw-rw----@ 1 root admin 16216 30 Mar 09:01 mdworker
2010-03-30-090154localhost.crash
-rw-rw----@ 1 root admin 9138 30 Mar 09:01 lsregister
2010-03-30-090154localhost.crash
-rw-rw----@ 1 root admin 9114 30 Mar 09:25 lsregister
2010-03-30-092527localhost.crash
-rw-rw----@ 1 root admin 16216 30 Mar 09:25 mdworker
2010-03-30-092528localhost.crash
-rw-rw----@ 1 root admin 8551 30 Mar 20:51 lsregister
2010-03-30-205149localhost.crash
-rw-rw----@ 1 root admin 16217 30 Mar 20:54 mdworker
2010-03-30-205428localhost.crash
-rw-rw----@ 1 root admin 9115 30 Mar 20:54 lsregister
2010-03-30-205428localhost.crash
-rw-rw----@ 1 root admin 9892 30 Mar 20:56 coreservicesd
2010-03-30-205653localhost.crash
-rw-rw----@ 1 root admin 9893 30 Mar 20:56 coreservicesd
2010-03-30-205656localhost.crash
-rw-rw----@ 1 root admin 14456 30 Mar 20:57 mds
2010-03-30-205736localhost.crash
-rw-rw----@ 1 root admin 27947 30 Mar 20:57 loginwindow
2010-03-30-205742localhost.crash
-rw-rw----@ 1 root admin 15628 30 Mar 20:57 mdworker
2010-03-30-205754localhost.crash
-rw-rw----@ 1 root admin 9138 30 Mar 20:57 lsregister
2010-03-30-205754localhost.crash
-rw-rw----@ 1 root admin 10345 30 Mar 21:18 coreservicesd
2010-03-30-211816localhost.crash
-rw-rw----@ 1 root admin 9893 30 Mar 21:22 coreservicesd
2010-03-30-212205localhost.crash
-rw-rw----@ 1 root admin 9138 30 Mar 21:26 lsregister
2010-03-30-212617localhost.crash
-rw-rw----@ 1 root admin 9113 30 Mar 21:50 lsregister
2010-03-30-215050localhost.crash
-rw-rw----@ 1 root admin 16216 30 Mar 21:50 mdworker
2010-03-30-215052localhost.crash
The last two at 21:50 are from after the reboot, and here's the details from them:
Just installed 10.6.3 and it appears to have made things worse. Can't keep a finder window open for more than two clicks. eg - try open documents and it vanishes. Been praying they'd fix this for months. Have given up hope and am ready to bin my Mac. It's a joke. It just doesn't work.
It also mentioned external drives causing the issue, which other people have mentioned. I don't have any external USB/FW drives, but do have 2 NFS shares to a QNAP TS-219 NAS device. They're automounted using Disk Utility (File -> NFS Mounts...), so I removed those 2 entries and rebooted.
I also noticed that l had some log errors related to the Wacom Tablet driver and coreservicesd, so I downloaded the latest driver and reinstalled it.
The problem seemed to go away, so I re-enabled the NFS mounts, and created an empty .metadata
neverindex file on the root directory of the mounts like this:
cd /Volumes/Network/Qdownload
touch .metadata
neverindex
That should hopefully stop spotlight ever trying to reindex them. I got the filename from a macosxhints.com tip. Anyway, I've not had any more diagnostic dumps into /Library/Logs/DiagnosticReports in the last 90 minutes, so it's looking promising
Still no reappearance of the main problem here after installing 10.6.3 – but not out of the woods either. After well over 12 hours, Spotlight indexing doesn't appear to have made progress one bit – it's gone back to its original "79 hours remaining" estimate, and the blue progress bar hadn't moved.
jevlewt - is there any way to force a complete refresh of spotlight indexing? that is, clear out all its data and get it to start from scratch. if it's locked up and crashing due to bad data then it might help.
I am sitting with a big smile on my face as it is "so far so good" for the first time since last September. I have daisy chains of external hard drives all sitting whirring, moving events round between various computers and iPhoto libraries. External hard drives waking out of sleep. One EHDD (a Freecom 1TB FW400) which would not work at all, is working perfectly. I used the combo updater on all our machines. For safety, I have still got Spotlight disabled on external drives.
