Finder hangs up in El Capitan

I have installed and re-installed El Capitan on my Mac Pro 4,1 three times now because of intermittent Finder hang-ups that require rebooting. Each install has bee a "clean" install with migration of user and other data with migration assistant. The Finder hangs don't always recur with the same actions and seem to randomly occur when I am doing something such as clicking on an item in the main menu bar ("Edit", "File", etc.) or when working within an open window. I can work for an hour or more without a problem and then it occurs.


My preliminary observations seem to suggest that this only happens in my main user account, but I've not had enough time to explore this exhaustively.


How do I troubleshoot this? Any ideas on why this is happening.

Mac Pro

Posted on Oct 6, 2015 11:14 AM

Reply
14 replies

Oct 6, 2015 3:41 PM in response to John Baughman

Hey there John,


I see that you are having a recurring issue with El Capitan and have tried to resolve the issue by reinstalling the OS then migrating user data. As you have suggested in your post, it may be useful to test this behavior in a new user account. I have an article that can help you accomplish this testing, and it is linked below:


How to test an issue in another user account on your Mac - Apple Support

https://support.apple.com/en-us/HT204443


Thanks for coming to the Apple Support Communities!

Oct 6, 2015 4:05 PM in response to braden85

Thank you for that link. That is essentially the track I have been taking in troubleshooting this issue. I created a new user account and with much manipulation in that account I was able to confirm that the Finder did not freeze. I tried to think about what was different between the two accounts. I quickly realized that I had 4 startup items in my user account that had been migrated into the new El Capitan installation. These were of course not present in the new user I created for troubleshooting. I removed all 5 of these startup items and as you might guess, the Finder freezes ceased. Now I just need to slowly add back one item at a time to see which one is the culprit. I should have been suspicious about the startup items since several of them get installed in the main menu with startup.

The startup items in question are OpenDNS updater, a TechTool Pro startup item, Dropbox, Remotix (a remote connection app), and a menu item for Transmit.

Thanks for taking the time to help me with this issue.

John

Oct 6, 2015 5:32 PM in response to John Baughman

When the Finder becomes unresponsive, note the exact time: hour, minute, second.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

The title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

When you post the log extract, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Oct 6, 2015 5:45 PM in response to Linc Davis

When I posted this issue I said to myself, "Maybe I'll get lucky and Linc Davis will respond". I actually used a response you gave to a similar question posted about 2 years ago to begin my troubleshooting. The one where you instructed the poster on generating information with 5 Terminal entries. This was extremely helpful to me. Using it and doing my own interpretation, I discovered that an app called Phone Amega was causing "kernel_task" to run constantly at > 100% CPU on my Mac Pro.


Fortunately ( or unfortunately, depending upon how you view it) I no longer have the Finder hanging problem so I can't follow your current instructions. I attribute the Finder hangs to indiscriminate installing of apps that provide limited function and require tweaking of the system by installing things in the main menu and elsewhere. When I disabled 5 non-essential login items the problem went away. I think I've learned my lesson. I will keep your instructions handy in the unhappy event that I have a recurrence of the Finder hanging thingy.


You are a great resource for the Apple Community. I have benefited on numerous occasions from your sage advice and input.

Thanks.

John

Oct 10, 2015 5:21 PM in response to John Baughman

I'm having the same problem but I solve it by killing the Unix process. If you're not familiar with using Unix commands you might want to explore a bit before trying this but this is what finds the Finder process and kills it. Then you can open a new Finder without re-booting.


ps aex | grep Finder


87151 ?? S 0:19.92 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder TMPDIR=/var/folders/m2/pt5fjnrs2nn5f3mlgg063wc00000gn/T/ SHELL=/bin/bash HOME=/Users/hellyj Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.vtlTt6xf6i/Render SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.iRtbOacQ3A/Listeners LOGNAME=hellyj PATH=/usr/bin:/bin:/usr/sbin:/sbin DISPLAY=/private/tmp/com.apple.launchd.hf9ZQxwuWZ/org.macosforge.xquartz:0 XPC_SERVICE_NAME=com.apple.Finder USER=hellyj XPC_FLAGS=0x1


kill -9 87151

Nov 24, 2015 7:43 AM in response to Linc Davis

Hello Linc Davis


I did what you advice to do in Console but there wasn't any log file from today date and time when Finder hangs up, last date was 4 days ago. Also there was info in Diagnostic and Usage Messages (that time and date when Finder hangs up), but it is useless because there is info about airport/wifi.


What should i do if Finder constantly freezes and i have no log files on location that you provide?


I was able to repeat Finder/Preview freeze, next log i took from Console, Diagnostic and Usage information/Diagnostic and usage messages tab:


11/24/15 17:35:58.524 Unknown[8169]: com.apple.message.domain: com.apple.assumes.failure

com.apple.message.signature: 3E09C275-A33B-357A-B0AB-A2DDF88EC9D5:79134

com.apple.message.signature2: 0x89

com.apple.message.signature3: libxpc.dylib

com.apple.message.summarize: YES

SenderMachUUID: B4EA1C9C-D6DF-3EFC-9B71-352ADB640494


There was only this log regarding failure, other concerned WiFi, Message accounts etc.

Dec 10, 2015 9:44 AM in response to John Baughman

I have 3 Macs all running Mac OS El Capitan. Macbook Air, Macbook Pro, iMac 27" (Work) with 2 extra screens attached. I've been on El Capitan since the first early beta releases on my Macbook Air.


The Macbook Air is the Mac that's done best... when I replace my old 2009 iMac (died) with a Macbook Pro – the Macbook Pro seemed very slow. Helped when I turned off FileVault. Works okay now.


But my iMac at work has had this strange problem after updating to El Capitan. Not from day one. Finder would suddenly become unresponsive. It happened couple of times... 3-4-5 a day. No other apps were affected and restarting finder would fix things. Since last MacOS update finder would restart itself – most of the times – when a finder crash occurred. Not always.


But... at this point – it's 3 days since finder has become responsive last time. I cross my fingers...


What I did was clean up all files on my desktop. Trashed some, put the rest in a folder. That's the only thing I've been doing... so I suspect a bad file somewhere on my desktop. Or... it could be something else or just plain luck. But I hope it last...


So... clean up your desktop. It seems to be the thing that did it for me. There's probably invisible files at your desktop as well... could be one of those as well – I think.

Dec 10, 2015 12:02 PM in response to John Baughman

I have had a similar problem but a little different. I start El Capitan and the Finder freezes for at least 5+ minutes. Programs open from a previous session, mail downloads but nothing responds to mouse clicks. After the above time period, the Finder suddenly works as normal and the mouse clicks become functional. I deleted two startup items. I deleted a BOINC start-up item as well as the BOINC app and an old Cinch item in the start-up menu. I left a newer Cinch start-up item and did not delete that app. Problem solved. So, thanks to John, I would suggest deleting unnecessary start-up items as he suggested.

Feb 18, 2016 12:04 PM in response to John Baughman

Similar problem here: Sometimes out of the blue finder does not react to Cmd+W commands. At least that's when I always noticed something was odd. Actually the window or tab closes a minute later but Finder stays unresponsive afterwards. I can resolve the problem by restarting Finder.


Console shows this (related to finder):

18.02.16 20:51:59,725 Finder[1346]: void CGSUpdateManager::log() const: 28 HIToolbox 0x00007fff8e195c48 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 404

18.02.16 20:51:59,725 Finder[1346]: void CGSUpdateManager::log() const: 29 HIToolbox 0x00007fff8e1ab9e6 SendEventToEventTarget + 40

18.02.16 20:51:59,725 Finder[1346]: void CGSUpdateManager::log() const: 30 HIToolbox 0x00007fff8e207852 _ZL15SendMenuOpeningP14MenuSelectDataP8MenuDatadjjP14__CFDictionaryhPh + 716

18.02.16 20:51:59,725 Finder[1346]: void CGSUpdateManager::log() const: 31 HIToolbox 0x00007fff8e221d24 _ZL11DrawTheMenuP14MenuSelectDataPP9__CFArrayhPh + 280

18.02.16 20:52:16,520 loginwindow[101]: Failed to write crash history to file:///Users/achim/Library/Application%20Support/CrashReporter/Finder_A583BA3A -FB07-5D60-9B7B-9487ADADC6AD.plist.

18.02.16 20:52:16,572 syncdefaultsd[17328]: com.apple.finder has been removed from syncing apps.

18.02.16 20:52:16,586 com.apple.xpc.launchd[1]: (com.apple.Finder[1346]) Service exited due to signal: Terminated: 15

18.02.16 20:52:17,090 Finder[17354]: assertion failed: 15D21: libxpc.dylib + 63930 [61AB4610-9304-354C-9E9B-D57198AE9866]: 0x89


Does this mean anything to one of you guys? Thanks in advance!

Mar 19, 2016 9:20 AM in response to hansenodense

I can report similar behaviour on a friend's iMac. She panics everytime it happens, and I iMessage -> Screen Share to her computer and Force Quit her Finder. Then it works a-ok for a while again.


Is there any chance 10.11.4 might fix this, or is there something I could do about this? She's beside herself and I can't seem to help apart from Force Quit.. That's not the Mac way.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Finder hangs up in El Capitan

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