Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does 10.9 suffer from same slow shutdown issue as 10.8?
- Thread starter Krazy Bill
- Start date
- Sort by reaction score
Hate to break it to you but it's certainly a possibility. Just because something is faster doesn't mean it's always the best way to do it. If that were the case you would just take the battery out/switch off the power at the wall whenever you wanted a 'faster shutdown' but since we all know this may lead to data corruption on the drives no one does this.
Maybe those faster shutdowns were causing more issues than what they fixed so they were slowed down to give processes more time to finish properly or a plethora of other reasons.
Interesting.
Then I apologize, you are quite correct. I did not know this was an actual technical problem. I blindly assumed you were all crazy when, in fact, there appears to be technical merit behind these concerns.
I checked and it appears as though securityd and appleevents consistently fail to shut down in a sane manner over here on my primary workstation. I have filed the relevant bug reports on radar, if you are a developer I would advise you do the same.
It is possible to check which processes are hanging up the shutdown by running the following command in Terminal.app:
Code:
cat /var/log/com.apple.launchd/launchd-shutdown.system.log | grep "Exit timeout"This will print out a list of processes that fail to shutdown within 20 seconds of being issued SIGTERM. I'm only seeing listings for com.apple.securityd and com.apple.coreservices.appleevents over here, this is highly dependant on your system software so these two may or may not be the source of your problems.
To "fix" your slow shutdown (this isn't really a fix), issuing these commands into Terminal.app should do the trick:
Code:
sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2
sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 1Again, this is not really a fix. You are setting the exit timeout to 2 and 1 second(s), and terminating the process after that time elapses (instead of waiting 20 seconds). These processes should exit cleanly within 20 seconds, and they are not- so this fix is kind of forcing things and you shouldn't need to do that.
Oddly enough, I just installed 10.8.4 inside a virtual machine to check out this issue, and it doesn't exist on a fresh install. Both securityd and appleevents terminate almost instantaneously, so there is something else hanging them up. The VM shuts down and restarts almost instantly. securityd is actually part of the Security project, the source code for which is available on opensource.apple.com. It is a relatively simple utility, but from what I can see there should be no reason why it would hang up and refuse to quit when signalled with SIGTERM- so I'm guessing there is some sort of deeper issue within CoreFoundation that needs to be researched and fixed.
In any case, the only thing I can recommend at this point is to let Apple know about it. If this stuff really bugs you, you can always run the two above commands (the ones with `defaults` in them). This should fix the issue, but it's not an ideal solution at all.
-SC
Whatever the issue it didn't exists in the ML GM and later 10.8.1. Something changed in 10.8.2 and from then on it only got worse. Also the fact that same issue exists in the 10.9 dev preview … don't get your hopes high.
Last edited by a moderator:
Many of us have developer accounts and have reported the problem since September of 2012 (and earlier). I've submitted console logs. Apple does indeed know about this. Suffice it to say, I've given up.
Chasing an issue that's hard to replicate is one thing (been there), but choosing not to fix one that can be reproduced on practically every reboot is another - it's actually mind boggling.
Is the slow shutdown a showstopper? No. But this bug merely gives one insight into the cranial workings of the OSX team and their methodology (or lack thereof) which in turn makes one scratch his/her head about all the other nuances in OSX they are charged with. To me, THIS is the interesting part and very telling.
What about all of us folks using SL (and its quick shut downs) for years without a problem, don't you think we would have noticed?
The "wasting money and electricity" doesn't work for me. The math is pretty simple and I wont bore anyone with it. But the basic facts are this....
iMac On: 80W
iMac Sleeping: 1W
iMac Off: .2W
Cost of Electricity (Southern California): $0.14/kWh
The basic math shows that the difference between OFF and SLEEPING is 2.4W over 12 Hours, OR $0.00112. In other words, a sleeping iMac (27", Core i7 with 16GB ram) takes 24 hours to use the same amount of power as a child's night-light uses in 1 hour. Or, 12 hours of sleep is the same as 8 minutes of running with all 4 cores and GPU maxed out.
I don't power down my Macs at night. I don't see the need. Besides, 75% of what you would save is simply wasted in the amount of time it takes to power off at night, and back on in the morning.
iMac On: 80W
iMac Sleeping: 1W
iMac Off: .2W
Cost of Electricity (Southern California): $0.14/kWh
The basic math shows that the difference between OFF and SLEEPING is 2.4W over 12 Hours, OR $0.00112. In other words, a sleeping iMac (27", Core i7 with 16GB ram) takes 24 hours to use the same amount of power as a child's night-light uses in 1 hour. Or, 12 hours of sleep is the same as 8 minutes of running with all 4 cores and GPU maxed out.
I don't power down my Macs at night. I don't see the need. Besides, 75% of what you would save is simply wasted in the amount of time it takes to power off at night, and back on in the morning.
Neither do I. When I'm at home. But try traveling 300-400 miles in a day with a dozen stops - each requiring either:
A.) Sleep, or...
B.) Shut Down
I'd prefer "A" but over the course of a long day I lose at least 10-15% battery (at least). This often makes all the difference between a necessary adapter plug-in. So... I shutdown and reboot between stops.
Recently though, when on the road I've just set my startup drive to a Windows 8 partition. 2-3 seconds shutdown max. My battery life is about 30 minutes longer as well.
All this is moot though. OSX should shutdown quickly like it did in the past. (If only because it's a bug that should piss off any rational-thinking coder). Those of us who have habits that rely on this, good for us - those that don't care can just continue to ignore it.
Installed Mavericks today. It's just as bad as Mountain Lion.
The thing is, I bought this Mac Mini (late 2012) for my office, and sometimes I like to bring the Mac Mini home to watch Netflix or whatever on my big screen.
So at the end of the day, sometimes I'm standing around for a minute feeling like an idiot waiting for it to shut down.
My 2009 Snow Leopard machine was off in 5 seconds flat.
I'm grateful for Mavericks (its much snappier than Mountain Lion... which made this new Mac run slower than my SL Mac...
)
The thing is, I bought this Mac Mini (late 2012) for my office, and sometimes I like to bring the Mac Mini home to watch Netflix or whatever on my big screen.
So at the end of the day, sometimes I'm standing around for a minute feeling like an idiot waiting for it to shut down.
My 2009 Snow Leopard machine was off in 5 seconds flat.
I'm grateful for Mavericks (its much snappier than Mountain Lion... which made this new Mac run slower than my SL Mac...
)Yes, 10.9 lags with shutdown just like 10.8.4. It appears to be Launchd processes again, and the same ones!
Note that the shutdown issue is fixed in 10.8.5 12f17. So far, I haven't seen it do a slow shutdown yet, no matter what apps are running in the background on my friend's beta machine; it shuts down completely cold in less than 5 seconds. Unless something changes with the next preview, I think 10.8.5 is set.
Following the same trend, I expect 10.9 will be fixed at some point.
Note that the shutdown issue is fixed in 10.8.5 12f17. So far, I haven't seen it do a slow shutdown yet, no matter what apps are running in the background on my friend's beta machine; it shuts down completely cold in less than 5 seconds. Unless something changes with the next preview, I think 10.8.5 is set.
Following the same trend, I expect 10.9 will be fixed at some point.
Have you guys tried beta 2 of 10.8.5? On my ssd machine the problem has gone away permanently. I confirm that mavericks dp2 is still slow, however.
Not even the terminal commands to kill the stuck processes worked for me in 10.8.4...slow as molasses to shut down .
Not even the terminal commands to kill the stuck processes worked for me in 10.8.4...slow as molasses to shut down .
Do you have an SSD, Retina or Macbook Air?
The main point is that SSD and Flash mem users notice the shutdown anomaly more since the machines boot and shut down so fast already....or at least they're supposed to.
Not sure if Retina or Air users have slow shutdown problems with 10.8.5. How about it guys? Anyone confirm?
Last edited:
I guess I'm about ready to give up on this issue too. Slow shut down is back in 10.8.5 12f20; clearly the lack of it in 12f17 was something unique to my machine.
They closed a recent bug report filed by someone I know on this issue as a duplicate, saying "there was no more information available"
I'm going to keep digging at it, I guess.