macbook pro slow shutdown 10.8.2

Today I had to add

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 2

which caused a timeout...

....and tomorrow, you'll have to add something else.... and tomorrow.... and tomorrow....

Are the Apple Software Engineers already on Christmas vacation, which started on September 19th when the update was released that introduced this problem?

Yeah. Don is exactly right. This issue has multi causes that all relate to shutdown items that must be timed out by the operating system. I've done every fix in this thread and I shutdown my Macbook Air twice a day (once at home and once at work). I'm now seeing about 30% fast shutdowns (<= 3 seconds) and 70% slow shutdowns (40-45 seconds) vs. 100% fast shutdowns when I used Lion.

Why is this taking so long? It's now been 5-6 months since Mtn Lion was issued. Unfortunately, I think that eye-candy issues (like the new iTunes) are far more important than substantive issues like this one.

Scott Newman wrote:

Why is this taking so long? It's now been 5-6 months since Mtn Lion was issued. Unfortunately, I think that eye-candy issues (like the new iTunes) are far more important than substantive issues like this one.

unfortunately i agree with you scott. good thing is, there was a problem (bug or intentional feature removal? it's tough to say these days) with itunes 11 where users are unable to search their ipod libraries which has been corrected in the latest update.

but it's a bit absurd to think that anything could possibly be more pressing than basic OS functionality. and how did the 10.8.2 seed that was being tested before it was released ever make it public with this kind of glaring problem?

Below is everything it said in Console at the time of shut down. If someone can interpret this for me it would be great!

11/12/12 2:24:07.127 PM WindowServer[71]: dict count after removing entry for window 0x1d is 0

11/12/12 2:24:07.137 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.137 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.138 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.138 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.138 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.143 PM com.apple.launchd[1]: (com.apple.ShareKitHelper[570]) Exited: Killed: 9

11/12/12 2:24:07.144 PM com.apple.launchd.peruser.501[121]: ([0x0-0x10010].com.apple.inputmethod.ironwood[173]) Exited: Killed: 9

11/12/12 2:24:07.152 PM coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=159

11/12/12 2:24:07.156 PM com.apple.launchd.peruser.501[121]: ([0x0-0xb00b].com.apple.iTunesHelper[164]) Exited with code: 1

11/12/12 2:24:07.155 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.155 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.156 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.156 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.156 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.157 PM com.apple.launchd.peruser.501[121]: ([0x0-0x22022].com.apple.AppleSpell[221]) Exited: Terminated: 15

11/12/12 2:24:07.157 PM com.apple.launchd.peruser.501[121]: (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[985]) Exited: Killed: 9

11/12/12 2:24:07.159 PM coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=167

11/12/12 2:24:07.159 PM coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=767

11/12/12 2:24:07.159 PM coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=140

11/12/12 2:24:07.187 PM loginwindow[53]: DEAD_PROCESS: 53 console

11/12/12 2:24:07.245 PM airportd[1038]: _doAutoJoin: Already associated to “Airport Express - LAJSR”. Bailing on auto-join.

11/12/12 2:24:07.407 PM coreservicesd[31]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=129

11/12/12 2:24:07.409 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.409 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.410 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.410 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.410 PM WindowServer[71]: CGXGetConnectionProperty: Invalid connection 45571

11/12/12 2:24:07.430 PM shutdown[1039]: halt by Rich:

11/12/12 2:24:07.430 PM shutdown[1039]: SHUTDOWN_TIME: 1352748247 430131

RMSko, if you want a deeper understanding about the nature of the shutdown stalling please go back & read the entire thread... or at least the last four pages or so. we are all in the same boat here and it won't do much good for anyone to read & interpret the console log you posted. if there were anything useful to be gleaned it would not be there but rather in the sidebar under:

/var/logs/

com.apple.launchd

launchd-shutdown.system.log

look in there and and filter results (filter in upper right window corner) for the word "killing". this should show you precisely which process stalled at shutdown. be be advised that there are seemingly a multitude of different corservices which may or may not stall randomly at shutdown.

if you want a quick fix, my advice is go into terminal and use OlliHappyOnMac's workaround, which is more or less:

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 2

sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 2

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 2

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 2

if you're not familiar with terminal basically just copy and paste each of those 5 lines one at a time. you will need to enter your password (assuming you are an admin) after the first one. there was some discussion about file permissions and plist formats being changed by this method but it is now my opinion that it doesn't affect anything. if you're at all concerned you can run repair disk permissions in disk utility afterward. this is only a workaround and in no way, shape or form address the root cause of the shutdown stalls... but it should get your computer to behave better in the short term.

best of luck! hope this helps.

Thanks so much billy. It seems I have the following 2 things that are delaying shutdown:

20004971 com.apple.launchd 1 com.apple.securityd 15 Exit timeout elapsed (20 seconds). Killing

20007096 com.apple.launchd 1 com.apple.coreservices.appleevents 62 Exit timeout elapsed (20 seconds). Killing

I guess my problems are with "securityd" and "appleevents". I've seen that others have the appleevents problem, I'm not sure about securityd. I may give your other suggestions a shot.

You could spend a lot of time trying to fix this, but eventually, you will experience it again, as all of us have, because it's not something that appears to be fixable by simply killing the processes that are delaying shutdown, because they aren't always the same, even on the same Mac.

Hi RMSko,

this are exactly the symptoms I saw on my macs with Mountain lion.

Just enter the commands I suggested in Terminal and repair the disk permissions afterward.

Ok and it's been months since last update and why hasn't Apple come up with a fix for this? Everywhere you try to look for this issue as in other sites or in the news it never appears . Its like Apple try's to hide everything from the media. They rather pay the media more money to hide the truth from the world than actually spend money and apply a quick fix for this. This is my first Mac ever and I'm not such a Mac fan like i was the first day I received my Mac book air 2012 13" .

Yeah...people with MacBook Airs or people that use SSDs are the ones who really notice this bug. Going from 2 to 3 seconds every shutdown to 30 to 40 seconds is huge.

You know that the OSX development team at Apple involves at least some employees who use SSDs in their Macs--so they clearly know about this. On the other hand, the longer that this goes unfixed, the more it speaks about the priorities at Apple right now.

To give the guys at Apple a little bit of a break, they might not even bother to shut down their computers at the end of the day. However after all these complaints about the shut down, surely one of them would have shut down their computer, just to see what it is all about.

Contacted the support today, to get an answer to the problem. They sent me an diagnosis tool. Sent back everthing and hopefully they will do something. First reaction of the support was: "this problem is unknown"!!!

I suggest to do the same if you're in the 90 days support period.

it is difficult for me to believe that support has no awareness of a thread which continues to stay on the first page of the Apple's own Mountain Lion discussion forum, has over 100 replies & is pushing 19000 views.

that is either total BS or they are surprisingly incompetent. either way it's bad news.

Hey guys!

I searched the net for a fix to this issue since I have it as well and google brought me to this thread. I tried to look in the specific logs in console (launchd-shutdown.system.log and the one next to it) but I found nothing. I searched for the words 'timeout' and 'killing' and I got nothing. Thing is, I have the 30-45 seconds shutdown issue and I don't know why.

Any idea of what could help me? Thanks!