Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

printz

macrumors regular
Dec 23, 2012
218
0
I think it's an ugly bug & shameful to leave unfixed for so long.

I always assumed it's just OS X being so bloated ever since Lion, that shutting down would take this long (lots of house cleaning to do). On my Snow Leopard Macbook, it shuts down in a second.
 

th-gates9345

macrumors member
Sep 15, 2011
30
24
Go back to 10.8.1

Is there a way to go back to 10.8.1? No problem at all for me with that version, and it's the last one with acceptable shutdown time.
 
Last edited:

andrezuppe

macrumors member
Apr 19, 2010
50
2
Genoa, Italy
Shutdown / reboots slooow again

Upgraded to 10.8.3 hoping to find a fix for that problem...
After the first 5-6 "almost instant" reboots, my 15" retina MBP became again slow as 10.8.2 (15-20 seconds of spinning wheel on grey screen, then shutdown).

It's a shame to have a mac that boots in 8 seconds and shutdown...in 20!! :mad:

My 2010 MBP 13" c2d with a 5400rmp HDD with snow leopard 10.6.8 reboots / shutdown in 1 second.

I don't understand. :(

Bye,

Andrea
 

UBS28

macrumors 68030
Oct 2, 2012
2,893
2,340
my shutdowns are 4-5 secs.. if you don't have ssd don't expect to get miracle from your computer

A MBP with a SSD running Mountain lion shuts down slower than a MBP with a HDD running Snow Leopard ( which is almost instant shut down). In boot up the difference is huge though ( in favor of the SSD + Mountain Lion ).

Something is wrong with Mountain Lion?
 

andrezuppe

macrumors member
Apr 19, 2010
50
2
Genoa, Italy
A MBP with a SSD running Mountain lion shuts down slower than a MBP with a HDD running Snow Leopard ( which is almost instant shut down). In boot up the difference is huge though ( in favor of the SSD + Mountain Lion ).

Something is wrong with Mountain Lion?



This is the thing I really don't understand!! :confused:

I have both with same softwares installed (no crap, no strange program installed, mac are both clean)... I think there's something in ML.
Bye,

Andrea
 

billynoah

macrumors newbie
Mar 18, 2013
2
1
I'm back to the infamous terminal dance... the Apple Two-Second Two-Step:

sudo launchctl unload /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist

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

sudo launchctl load /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist

This gives a relatively quick shutdown but it pisses me off I have to use it. (Also, I'll have to do it again any time permissions are repaired).
just did the update and all of my plist edits are unchanged (i.e. still set for 2 seconds). just curious, did yours change back to 20 seconds after the update? or is this a clean install?

also, i'd like to mention that after editing all these in 10.8.2:

com.apple.securityd
com.apple.coreservices.appleevents
com.apple.coreservices.appleid.authentication
com.apple.mDNSResponder
com.apple.diskarbitrationd

my shutdown times had significantly improved. however i was still getting an occasional 25 - 40 second stall approx 20% of the time so i changed to verbose boot mode (which also gives a verbose shutdown) to see what where exactly the stall was happening. interestingly since changing the boot args to verbose i haven't had a single slow shutdown in over a month. i have no idea if this is pure coincidence but felt it's worth mentioning.

updated to 10.8.3 today and still consistently getting 5 - 10 second shutdowns. for me this is acceptable.
 

Lunchb0x8

macrumors 6502a
May 2, 2010
604
35
Quirindi, NSW, AU
I found what was causing it for me.

appleevents.plist
appleid.authentication.plist
dock.plist
securityd.plist

These and one that was apparently related to my account.

The one linked to my account was some drivers and apps for a canon printer I have never installed, so I removed the drivers and apps, fixed the above plists with the timeout fix and then booted into recovery and did a disk repair.

So far, 3-4 second shutdowns.
 

nangariel

macrumors member
Oct 18, 2011
44
0
I don't get this at all... When I run 10.6.8 from an external HDD, my MB shuts down in 4 seconds (every time). When I run 10.8.3 from an internal SSD, the shutdown time can be seemingly randomly anything between 2 and 22 seconds :(
 

justperry

macrumors G5
Aug 10, 2007
12,627
9,933
I'm a rolling stone.
I don't get this at all... When I run 10.6.8 from an external HDD, my MB shuts down in 4 seconds (every time). When I run 10.8.3 from an internal SSD, the shutdown time can be seemingly randomly anything between 2 and 22 seconds :(

The problem is that some services don't shut down and have to be killed, if you want to see it hold Command-V at startup, this will allow you to see what the system does, when you shut down the Mac it will show text again and you'll see what's going on.
Try it.
 

adnbek

macrumors 68000
Oct 22, 2011
1,584
551
Montreal, Quebec
Really ? 7-10% at sleep ?

When I put my MBA 2012 to sleep and wake it up like 8-9h later, the battery is still 100%.

MBAs and rMBPs are different. They go into deep sleep (move all RAM content to SSD) and drain very little battery. Not so with the original MBPs. Those drain about 1% per hr approximately while on standby because RAM is still being powered.

----------

I don't understand responses in this thread saying "why shut down at all" and "how does that affect you?". It doesn't matter and it's none of anyone's business how they choose to use their computer or not. If they shut down every day, so be it. If they restart into Bootcamp every day, so be it. The restart/shut down mechanism is broken and that's all that matters. 10.6 and 10.7 would shut down in a second while ML shuts down in 20. To me, that's a bug and it should be fixed regardless of how often a person shuts down or not.

And FYI, I have a mini which I almost never shut down, so the issue doesn't affect me much personally. But I'll still say it should be fixed instead of jumping on that complacent bandwagon and say "so what?".
 

adnbek

macrumors 68000
Oct 22, 2011
1,584
551
Montreal, Quebec
my shutdowns are 4-5 secs.. if you don't have ssd don't expect to get miracle from your computer

Nothing to do with SSD. The problem exists on both SSD and mechanical drives running ML.

And even on mechanical drives, shut downs were 2-3 seconds tops on previous versions of OSX. I'm willing to bet you're not using ML.
 

printz

macrumors regular
Dec 23, 2012
218
0
Bah, Windows XP also has a notably long shutdown time. What I mean by this, is that there can always be the odd OS version that has trouble shutting down.
 

Krazy Bill

macrumors 68030
Original poster
Dec 21, 2011
2,985
3
Everyone...

1.) Reboot your machines
2.) start the "Console" app (use spotlight to find it)
3.) in the String Matching search box enter: exit timeout

It will list those processes that were "force" terminated during the last reboot because they timed out.
 

cubbie5150

macrumors 6502a
Mar 4, 2007
716
224
Everyone...

1.) Reboot your machines
2.) start the "Console" app (use spotlight to find it)
3.) in the String Matching search box enter: exit timeout

It will list those processes that were "force" terminated during the last reboot because they timed out.

I just did that on the rMBP in my sig (which was built in Dec 2012 & came loaded w/ 10.8.2; I updated to 10.8.3 using combo updater):


Mar 23 01:12:03 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[136]): Exit timeout elapsed (20 seconds). Killing
Mar 23 02:03:36 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[489]): Exit timeout elapsed (20 seconds). Killing
Mar 23 12:06:05 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1159]): Exit timeout elapsed (20 seconds). Killing
Mar 23 15:28:33 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[137]): Exit timeout elapsed (20 seconds). Killing
 

printz

macrumors regular
Dec 23, 2012
218
0
Mar 23 01:12:03 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[136]): Exit timeout elapsed (20 seconds). Killing
Mar 23 02:03:36 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[489]): Exit timeout elapsed (20 seconds). Killing
Mar 23 12:06:05 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1159]): Exit timeout elapsed (20 seconds). Killing
Mar 23 15:28:33 <snip>-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[137]): Exit timeout elapsed (20 seconds). Killing

Ugh. OS X really buggy now. As I said, that really reminds me of Windows where certain processes would fail complying to the shutdown signal...
 

adnbek

macrumors 68000
Oct 22, 2011
1,584
551
Montreal, Quebec
Everyone...

1.) Reboot your machines
2.) start the "Console" app (use spotlight to find it)
3.) in the String Matching search box enter: exit timeout

It will list those processes that were "force" terminated during the last reboot because they timed out.

You need to do this search in console under /var/log/com.apple.launchd/launchd-shutdown.system.log and not under All Messages to see what's holding up shutdown. Any other "exit timeout" errors not in this log take place during normal operation.

In my case, the usual suspects: appleevents and securityd.
 

Krazy Bill

macrumors 68030
Original poster
Dec 21, 2011
2,985
3
You need to do this search in console under /var/log/com.apple.launchd/launchd-shutdown.system.log
Yes. Thank you for adding that. I forgot. :eek:


And speaking of appleevents... I changed my timeout thusly:

sudo launchctl unload /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist

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

sudo launchctl load /System/Library/LaunchDaemons/com.apple.coreservices.appleevents.plist

Except for the occasional 20 second anomaly I get about a 4 second shutdown time. It's been holding for a week or so. (Still pisses me off I have to do this though).
 

1member1

macrumors 6502
Sep 8, 2012
383
0
Nothing to do with SSD. The problem exists on both SSD and mechanical drives running ML.

And even on mechanical drives, shut downs were 2-3 seconds tops on previous versions of OSX. I'm willing to bet you're not using ML.

I got retina 13 running ML...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.