You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

finder crashes with maverick

Installed Mavericks and shortly thereafter Finder crashed. Error message keeps appearing, click OK to send to Apple and message returns. Tried restart to no avail. Any suggestions?

iMac, OS X Mavericks (10.9)

Posted on Oct 23, 2013 10:25 AM

Reply
128 replies

Nov 4, 2013 4:02 PM in response to data_bee

same here...


just found this on the google site:



This looks like the work of a new feature in OSX 10.9 -- automatic application termination. Basically, applications that are in the background and doing no work are terminated by OSX. Of course, OSX still supports background daemons, but if your background program is not setup quite right, the system treats it as a candidate for being terminated. Sort of a "tree falls in the woods" scenario. The application is not visible and not running and restartable, so why leave it laying around?

Google will have to address this.



Go to the Applications Folder and locate and select the Google Drive image. "Get Info" (cmd-I, or use right-click Get Info). Check the box "Disable App Nap", and you'll see that Google Drive no longer exits.


Nov 4, 2013 4:58 PM in response to applezen

I got the same problem today while backing up my files, the back-up task just can't be done because the finder kept refreshing itself so that the process has been interrupted. After reading the threads here I tried to stop the Google Drive app that used to be on while doing the backing-up, then the situation becomes normal again. It looks like 'cloud' like drives that are communicating with servers trigger the refreshing, and not sure if the bugs lie in Maverick Finder or Cloud Drives. Any suggestions?

Nov 4, 2013 5:10 PM in response to applezen

To everyone having trouble with Google Drive or any other cloud service, this thread is NOT about this issue. It's about finder crashing repeatedly and not even launching since the computer startup and the crashreport task kills the CPU, in Mavericks. This is not about the issue people are having today in which Finder restarts automatically, out of sudden.


tl;dr this thread is about a Finder issue found in Mavericks, which does not allow it to start.



EDIT: That's what the orginal thread issue looks like(picture):
User uploaded file

Nov 4, 2013 6:08 PM in response to applezen

For everyone who has upgraded & is having issues try EtreCheck…

http://www.etresoft.com/etrecheck


It was created for this very situation. It will generate a system report that may highlight what is happening with your system.


Post the report here for feedback or read this page for info on what the report sections mean…

http://www.etresoft.com/etrecheck_story



Mavericks has major stability issues with older code, specifically…


Startup Items:

Inside /Library/StartupItems/

These have been discontinued by Apple since Mac OS 10.4, but still people have them installed! They are responsible for making changes at a system level. Remove them all or spend time ensuring ALL related software is up to date. You need a very good reason to have anything installed in here.


Kernel Extensions:

Inside /Library/Extensions/

These also load third party code, but they insert it into the 'core' of the OS. These can be safe, however you must ensure the related tools or apps are up to date, otherwise the system is basically built upon quicksand. Remove them all & see if the OS works better.


Launchd jobs: several types

LaunchAgents - Stored in /Library/LaunchAgents

LaunchDaemons - Stored in /Library/LaunchDaemons

User LaunchAgents - Stored in /Library/LaunchAgents


These are all background jobs, they are not necessarily bad, but if they are loading old code it could be doing untold damage to the performance & stability of the entire OS. Focus on the System level jobs (the ones inside /Library - the system level) & 'failed' jobs.


EtreCheck gives a status on launchd jobs…

[loaded] - a running job

[not loaded] - jobs that are set not to run, basically harmless, remove them unless you plan to use the associated software (if it is up to date)

[failed] - jobs in a crashed or unknown state, it could be forking processes or using all the system resources, remove these


User login items:

Applications and helpers that are managed inside 'Systems Preferences > Users and groups > Login Items tab'.

These are loaded at the 'User level', consider removing all of them whilst you troubleshoot. When you decide to re-add them ensure the software is up to date.


3rd Party Preference Panes: & Internet Plug-ins:

/Library/PreferencePanes/ and ~/Library/PreferencePanes/

/Library/Internet Plug-Ins/ and ~/Library/Internet Plug-Ins/

~/ is your home folder, use the Finders 'Go menu > Go to Folder…' to open the hidden ~/Library folder.

Once again these items all must be up to date, or remove them from your system. If the prefpanes manage additional software use the uninstaller or see the developers site for uninstall instructions.


Read the list of plug-ins carefully, there are often duplicate Flash player versions that won't help stability, it's just wasted space too.

Top Processes by Memory:

Top Processes by CPU:

'Memory & CPU hogs' will be shown here - if it is using a huge amount of RAM or CPU, check it is up to date.


Virtual Memory Statistics

How much memory is being used for applications & services on the computer.

The critical items to look at are:

page-ins - writing files from disk to memory (this is completely normal)

page-outs - writing memory to disk. This is a slow process, it's a sign your machine has run out of RAM.




Have a known good backup before you modify the system, reboot after removing anything that loads as the system, basically anything inside /Library. You can move the files in question to another disk or folder if you want to be extra careful, just make sure the original files don't still exist.


I hope that helps someone here. Post the report for assistance, but try the above first.

finder crashes with maverick

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.