PDA

View Full Version : 10.8.3 (and 10.8.4b?) Still slow shutdown




Krazy Bill
Mar 14, 2013, 07:09 PM
20 second shutdowns persist. From the login screen! :eek:



Peace
Mar 14, 2013, 07:13 PM
Get over it.

:rolleyes:

GGJstudios
Mar 14, 2013, 07:15 PM
Why shut down at all?

JohnDoe98
Mar 14, 2013, 07:33 PM
Why shut down at all?

Dual boot for games?

SR45
Mar 14, 2013, 07:35 PM
6 shut down test using the logoff screen method over the keyboard method after a complete reformat and reinstall of OS 10.8.3 and all tests were 3 seconds. :6

Updated

Nielsenius
Mar 14, 2013, 07:36 PM
There's actually a manual fix for it. You change a value in some .plist or something. I did it a while ago. Search Google and you'll probably find it.

Mr. Retrofire
Mar 14, 2013, 07:54 PM
20 second shutdowns persist. From the login screen! :eek:
If you shutdown your Mac from the LOGIN screen, then you have some “other” serious problems. ;-)

----------

5 shut down test using the logoff screen method over the keyboard method after a complete reformat and reinstall of OS 10.8.3 and all tests were 3 seconds. :D
Yeah, that's a good & clean solution.

cmChimera
Mar 14, 2013, 08:20 PM
Dual boot for games?

Extra few seconds going to really bother you that much? Drink a mountain dew.

JohnDoe98
Mar 14, 2013, 08:31 PM
Extra few seconds going to really bother you that much? Drink a mountain dew.

I don't do games, was just answering a question. Either way for some people there is an issue there.

Peace
Mar 14, 2013, 08:34 PM
Anybody remember when Apple said they were going to have fast O/S switching ?

zakee00
Mar 14, 2013, 08:40 PM
Get over it.

:rolleyes:

No. I paid $2.5k for a device with buggy software. Apple's fit and finish seems to be waning.

Krazy Bill
Mar 14, 2013, 09:35 PM
If you shutdown your Mac from the LOGIN screen, then you have some “other” serious problems.Uh... no.

I was merely trying to see if OSX was taking so long to shutdown because it was killing other apps first like, Dropbox, Skydrive, etc. Doing a shutdown prior to loading these things seems like a logical test. (i.e., shutting down from the login screen).

cubbie5150
Mar 14, 2013, 10:51 PM
Yep, still slow shutdown in 10.8.3 for my rMBP.. Hell, it still changes my wallpaper on re-boot...as well as deleting folders I add into Desktop & Screen Saver in System Preferences. I don't even care anymore. I actually LOL that my $2500 rig can't even handle these miniscule details.

bkends35
Mar 14, 2013, 11:27 PM
Mine has gotten slightly better, now it takes 5-10 seconds.

Still could be better though.

Donka
Mar 15, 2013, 05:05 AM
Posts #92, 95 & 96...


http://forums.macrumors.com/showthread.php?t=1414639&page=4

Gator Bob
Mar 15, 2013, 06:12 AM
Mine has gotten slightly better, now it takes 5-10 seconds. Still could be better though.


I am truly curious ... why does this matter in the slightest?

Mike MA
Mar 15, 2013, 06:22 AM
20 second shutdowns persist. From the login screen! :eek:

Not sure if you face a different problem than - but I know you've been involved in the topic for quite some time.

I still face the problem occasionally under 10.8.3 - after using Airplay on a extensive basis. So for me it's not fixed.

Either from the login screen or when only surfing/checking mails the shutdown takes under a second as usual for an SSD drive.

SR45
Mar 15, 2013, 07:38 AM
I am truly curious ... why does this matter in the slightest?

It matters to me since we had a very short shut down with the other versions, and since it was no longer the case with 10.8.2, we felt that something was wrong with the OS, and needed fixing.

We like a short shut down so those that do it, would like to leave the computer sooner rather than later, and turn it off to do something else. With 10.8.2, I had to wait until it was shut down so I could turn off the system completely as a safety measure when I leave my home. 20 seconds may not mean much to you, but it does mount up over a short period of time. And no I will never just put my system into a Sleep Mode.

Even Microsofts Windows has a very short shutdown.

If you don't mind it, good for you, but please stop bad mouthing those that do want a better faster system. :p

6 times now, using the Log Off screen, the time needed is about 3 seconds.

Edited: More activity and now my shut down is around 20 seconds again :mad:

1member1
Mar 15, 2013, 08:01 AM
my shutdowns are 4-5 secs.. if you don't have ssd don't expect to get miracle from your computer

katewes
Mar 15, 2013, 08:02 AM
I am truly curious ... why does this matter in the slightest?

Right now, my near ancient 2009 MacBook Pro with a new SSD boots up in 12 seconds, and shuts down in 2 seconds with Lion 10.7.5.

That fast on and off are the difference between grabbing the computer to do a quick task that might take a few minutes - rather than say, nah, I'll do it later (particularly if the start and off takes 1-2 minutes like it did before I got the SSD.

All I can say is, you guys are mugs for being early adopters of Apples OS's. I'm not touching 10.8.3 with a 10 foot barge pole. Since 10.6, there's never been a .3 that's been rock solid. If 10.8.3 is rock solid, it'd be a first.

In my experience, 10.6 didn't come good until .6 -- however you wax lyrical about Snow Leopard, it was a dog at the beginning. Leopard was even worse. Lion has come good around 10.7.4. So if ML is great at .3, that'd be incredibly ... unlikely.

Krazy Bill
Mar 15, 2013, 08:33 AM
Below is my system log, right after shutdown. I'm listing only the "timeout" items that failed to close (they are the same as 10.8.2 for me):


Mar 4 09:29:39 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.quicklook.satellite.87B5D14A-38E6-4DA0-8894-87A34842D434[6845]): Exit timeout elapsed (20 seconds). Killing
Mar 4 11:28:12 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[7762]): Exit timeout elapsed (20 seconds). Killing
Mar 4 15:42:57 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[159]): Exit timeout elapsed (20 seconds). Killing
Mar 5 07:52:45 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.quicklook.satellite.5F27A930-AF25-4D05-A05C-AEF1F4966997[3338]): Exit timeout elapsed (20 seconds). Killing
Mar 5 09:08:49 rs-macbook-pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[163]): Exit timeout elapsed (20 seconds). Killing
Mar 5 09:10:03 rs-macbook-pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[465]): Exit timeout elapsed (20 seconds). Killing
Mar 6 13:01:18 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[6226]): Exit timeout elapsed (20 seconds). Killing
Mar 6 13:56:45 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[164]): Exit timeout elapsed (20 seconds). Killing
Mar 6 17:18:27 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[211]): Exit timeout elapsed (20 seconds). Killing
Mar 6 17:23:32 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[515]): Exit timeout elapsed (20 seconds). Killing
Mar 7 19:06:40 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[4292]): Exit timeout elapsed (20 seconds). Killing
Mar 9 13:21:51 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[241]): Exit timeout elapsed (20 seconds). Killing
Mar 9 18:51:30 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1967]): Exit timeout elapsed (20 seconds). Killing
Mar 9 18:52:11 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1971]): Exit timeout elapsed (20 seconds). Killing
Mar 9 18:52:23 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1963]): Exit timeout elapsed (20 seconds). Killing
Mar 9 20:42:57 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[2004]): Exit timeout elapsed (20 seconds). Killing
Mar 9 20:43:04 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1979]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:20:14 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[3983]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:20:33 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[3942]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:20:59 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[4042]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:20:59 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4024]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:21:20 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[4065]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:21:20 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4047]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:21:40 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4076]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:22:03 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[4095]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:23:09 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4123]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:23:29 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4148]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:23:49 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4163]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:24:09 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4171]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:24:29 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4188]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:24:49 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4202]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:25:18 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4222]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:25:38 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4232]): Exit timeout elapsed (20 seconds). Killing
Mar 10 10:25:58 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.qtkitserver[4251]): Exit timeout elapsed (20 seconds). Killing
Mar 10 20:26:58 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[6981]): Exit timeout elapsed (20 seconds). Killing
Mar 10 20:28:11 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[6997]): Exit timeout elapsed (20 seconds). Killing
Mar 12 15:37:58 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1192]): Exit timeout elapsed (20 seconds). Killing
Mar 12 15:11:33 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1406]): Exit timeout elapsed (20 seconds). Killing
Mar 12 15:34:26 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1553]): Exit timeout elapsed (20 seconds). Killing
Mar 12 15:34:59 rs-macbook-pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[1563]): Exit timeout elapsed (20 seconds). Killing
Mar 12 17:33:50 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[524]): Exit timeout elapsed (20 seconds). Killing
Mar 12 17:49:02 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[545]): Exit timeout elapsed (20 seconds). Killing
Mar 14 08:04:46 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[154]): Exit timeout elapsed (20 seconds). Killing
Mar 14 18:13:17 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[204]): Exit timeout elapsed (20 seconds). Killing
Mar 14 18:16:11 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[164]): Exit timeout elapsed (20 seconds). Killing
Mar 14 18:58:42 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[167]): Exit timeout elapsed (20 seconds). Killing
Mar 14 19:06:36 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[154]): Exit timeout elapsed (20 seconds). Killing
Mar 14 22:13:46 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[172]): Exit timeout elapsed (20 seconds). Killing
Mar 14 22:22:27 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[156]): Exit timeout elapsed (20 seconds). Killing
Mar 14 22:30:17 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[163]): Exit timeout elapsed (2 seconds). Killing
Mar 14 23:18:15 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coremedia.videodecoder[682]): Exit timeout elapsed (20 seconds). Killing
Mar 14 23:19:18 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[210]): Exit timeout elapsed (2 seconds). Killing
Mar 14 23:20:20 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[230]): Exit timeout elapsed (2 seconds). Killing
Mar 14 23:22:36 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[203]): Exit timeout elapsed (2 seconds). Killing
Mar 15 08:23:35 Rs-MacBook-Pro com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[154]): Exit timeout elapsed (2 seconds). Killing

trustever
Mar 15, 2013, 08:36 AM
Damn I was hoping that my 25 sec turn off lag would have been sorted with the 10.8.3...

----------

Below is my system log, right after shutdown. I'm listing only the "timeout" items that failed to close (they are the same as 10.8.2 for me):


Interesting point, when I get home I will check what mine looks like..

oldhifi
Mar 15, 2013, 09:31 AM
I have noticed my Imac shuts down faster now with ML 10.8.3.

trustever
Mar 15, 2013, 11:31 AM
I have noticed my Imac shuts down faster now with ML 10.8.3.

Did you upgraded with the combo or not? Any KP on restart? Ideally I would like to updgrade asap to sort the slow shot down but I am scared of potential KP...

oldhifi
Mar 15, 2013, 11:51 AM
Did you upgraded with the combo or not? Any KP on restart? Ideally I would like to updgrade asap to sort the slow shot down but I am scared of potential KP...

sorry I dont understand? what is combo? what is KP?

Krazy Bill
Mar 15, 2013, 11:51 AM
Why shut down at all?I sometimes travel 300 miles per day with up to a dozen different stops. Sleeping my machine through the day costs me about 7%-10% power.

Shutting down between those stops makes all the difference. And with an SSD the few seconds it used to take under SL worked just fine (Not to mention the extra battery life I got under SL to begin with).

Amazingly, I'm starting to shift into Windows 8 now using bootcamp during my travels. What a difference.

Get over it.Wow. Just wow. A console log riddled with blatant errors and I'm supposed to just "get over it"?

Just "get over" this thread son and exit.

trustever
Mar 15, 2013, 12:55 PM
Combo updates are those that can bring you to the latest version of the OS without the need to install intermediate version so you can pass from 10.8.0 to 10.8.3 with combo opposite to the delta update that will do 10.8.0-10.8.1-10.8.2-10.8.3

Kernel Panic is when you start up your mac and you will have a black screen with some white writings dettailing why the OS can not start properly but I assume from your questions that you

use the combo
did not have any KP

Which is great!

Krazy Bill
Mar 15, 2013, 02:57 PM
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).

Thirteen betas - plenty of feedback. Amazing. And to all you people who don't care about shutdowns and the other problems a few us in the minority do care about... well, what does this tell you about the OSX coders? These are the same people that keep your mac secure. :eek: Honestly, I'm surprised my machine actually boots with each freaking update these days and I'm beginning to think OSX is what the new coders practice on before they move on to more important things. (iOS)

Holy crap. :(

Tubamajuba
Mar 15, 2013, 04:57 PM
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).

Thirteen betas - plenty of feedback. Amazing. And to all you people who don't care about shutdowns and the other problems a few us in the minority do care about... well, what does this tell you about the OSX coders? These are the same people that keep your mac secure. :eek: Honestly, I'm surprised my machine actually boots with each freaking update these days and I'm beginning to think OSX is what the new coders practice on before they move on to more important things. (iOS)

Holy crap. :(

I've seen your posts quite a bit around here, and I'll say this- I really wish that Apple's coders had the same attention to detail that you do. OSX would be much better! Thing is, OSX is already plenty good, if not near-perfect, for some of us. I spent all of my computing life up until last August on Windows, and though I still view Windows in a positive light, I can't imagine going back on a daily basis. OSX is that awesome to me. So I think that's why people come across as unsympathetic when they respond to you- they're looking at the big picture whereas you see the smaller details.

So yeah, keep fighting the good fight, Krazy Bill. If it weren't for people like you, the development of OSX would be much more stagnant.

cooky560
Mar 15, 2013, 05:20 PM
same problem here, also, whats with the pointless (and timewasting) new animation before the login screen?

bkends35
Mar 15, 2013, 06:12 PM
I am truly curious ... why does this matter in the slightest?

My sisters MBP on 10.6.8 shuts down in 3 seconds with a 5400 rpm HDD, the SSD should take no time at all.

kensic
Mar 15, 2013, 06:31 PM
Why shut down at all?

why do people like to smoke? while others don't. it's all preference.

it's kind of annoying now that there's still people that just sleep their macs, trying to convince people that shut down their macs is wrong and it will have a negative impact on the computer.

stop with that nonsense. just let them do what ever they want. don't question it. when it is a perfectly legit method of what to do when the computer isn't in use.

madsci954
Mar 15, 2013, 06:45 PM
I tried shutting done my 2011 MBA (which I rarely do) and timed it. Once with some apps running and once with no apps running. 22 seconds both times from confirming Shut Down to totally off. Then 15 seconds from pressing the Power button to the Login Screen.

Edit: ML on 10.8.3, the machine originally came with Lion.

Update: I booted into Safe Mode, shut down, then booted normally. I did 2 more shut downs, the first took 4 seconds, the second 10. I didn't open any apps in between.

maxosx
Mar 15, 2013, 06:49 PM
Anybody remember when Apple said they were going to have fast O/S switching ?
I do.

However the problem may be all the time consuming law suits and other negative energy that's being wasted.

It's hard to be both positive and negative at the same time.

----------

I sometimes travel 300 miles per day with up to a dozen different stops. Sleeping my machine through the day costs me about 7%-10% power.

Shutting down between those stops makes all the difference. And with an SSD the few seconds it used to take under SL worked just fine (Not to mention the extra battery life I got under SL to begin with).

Amazingly, I'm starting to shift into Windows 8 now using bootcamp during my travels. What a difference.

Your points are well taken. However apparently Apple simply doesn't care :eek:

Badagri
Mar 15, 2013, 06:51 PM
Thirteen betas - plenty of feedback. Amazing. And to all you people who don't care about shutdowns and the other problems a few us in the minority do care about... well, what does this tell you about the OSX coders? These are the same people that keep your mac secure. :eek: Honestly, I'm surprised my machine actually boots with each freaking update these days and I'm beginning to think OSX is what the new coders practice on before they move on to more important things. (iOS)

Holy crap. :(

Also, this issue never happened with Lion. Ever. You can remind them on that.

My shutdowns vary with ML on an SSD, from 20 - 30 seconds, 8 - 12 hours in using OS X. Up to 50 seconds - 1 minute to shutdown. Upon a restart it can shutdown within 4 seconds but what good is that. But only takes 3 - 4 seconds to boot.

Even Windows 7 shuts down faster on a mechanical. Like 5 - 6 seconds.


Amazingly, I'm starting to shift into Windows 8 now using bootcamp during my travels. What a difference.


It shuts down within 1 - 3 seconds.

Saturn1217
Mar 15, 2013, 07:00 PM
Sigh...

Sad to see this didn't get fixed.

To those who say it doesn't matter:

I too hardly ever shut down my mac. You know when I do shut down my mac? When it freezes or something goes horribly wrong. There are some problems that require a restart and of course those problems only happen when you are say preparing for a presentation, or trying to show your boss something etc.

The point is that the really fast shut down time we used to have was really convenient in those situations where yes a few seconds do matter.

I still see videos all the time on youtube of people timing how fast their Macs start up from when you press the power button. All the people with SSDs loved to brag about this. But why does it matter if things take a few seconds longer?

...Because it is a computer and whenever it can be faster at doing a task without compromising batterylife or heat that is a good thing!

maxosx
Mar 15, 2013, 07:03 PM
Sigh...

Sad to see this didn't get fixed.

To those who say it doesn't matter:

I too hardly ever shut down my mac. You know when I do shut down my mac? When it freezes or something goes horribly wrong. There are some problems that require a restart and of course those problems only happen when you are say preparing for a presentation, or trying to show your boss something etc.

The point is that the really fast shut down time we used to have was really convenient in those situations where yes a few seconds do matter.

I still see videos all the time on youtube of people timing how fast their Macs start up from when you press the power button. All the people with SSDs loved to brag about this. But why does it matter if things take a few seconds longer?

...Because it is a computer and whenever it can be faster at doing a task without compromising batterylife or heat that is a good thing!
Kudos' for an excellent post.

For a company with the technical expertise of Apple, slow shut down times are unacceptable. It's as simple as that.

Badagri
Mar 15, 2013, 07:33 PM
Considering Microsoft can get it right. Start up 4 seconds, shutdown 2 seconds. Never thought I'd see the days of OS X in decline.

z06gal
Mar 15, 2013, 08:20 PM
Considering Microsoft can get it right. Start up 4 seconds, shutdown 2 seconds. Never thought I'd see the days of OS X in decline.


I have a 2 yr old desktop with Windows 7 on it that takes 45 secs to boot to the desktop. I have done everything I know but it doesn't change. Shutdown is about 10 secs but boot up is asinine :rolleyes:

Simplicated
Mar 15, 2013, 10:52 PM
same problem here, also, whats with the pointless (and timewasting) new animation before the login screen?

It's been there since Lion.


I have a 2 yr old desktop with Windows 7 on it that takes 45 secs to boot to the desktop. I have done everything I know but it doesn't change. Shutdown is about 10 secs but boot up is asinine :rolleyes:

Probably he's talking about Windows 8.

SR45
Mar 16, 2013, 03:54 AM
I sent another bug report on this, but I'm sure it will get nowhere fast as the last bug report did when 10.8.2 with the slow shut down was submitted. :mad:


Apple FeedBack Link

http://www.apple.com/feedback/

twintin
Mar 16, 2013, 04:52 AM
I sometimes travel 300 miles per day with up to a dozen different stops. Sleeping my machine through the day costs me about 7%-10% power.

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%.

th-gates9345
Mar 16, 2013, 09:33 AM
I've seen your posts quite a bit around here, and I'll say this- I really wish that Apple's coders had the same attention to detail that you do. OSX would be much better! Thing is, OSX is already plenty good, if not near-perfect, for some of us. I spent all of my computing life up until last August on Windows, and though I still view Windows in a positive light, I can't imagine going back on a daily basis. OSX is that awesome to me. So I think that's why people come across as unsympathetic when they respond to you- they're looking at the big picture whereas you see the smaller details.

So yeah, keep fighting the good fight, Krazy Bill. If it weren't for people like you, the development of OSX would be much more stagnant.

Agree.
Those Apple's extreme fanatics don't tolerate minimal critics to their "God Apple".
It's a kind of people that doesn't help to improve things.
-

mactoday
Mar 16, 2013, 10:14 AM
No. I paid $2.5k for a device with buggy software. Apple's fit and finish seems to be waning.
Welcome back to the new Apple, the old Microsoft style. btw: Safari now part of the OS X, you can't remove it without super tricks and super user rights.

FoolMeOnce
Mar 16, 2013, 11:25 AM
Welcome back to the new Apple, the old Microsoft style. btw: Safari now part of the OS X, you can't remove it without super tricks and super user rights.

Wow. Admin password is super rights?

Krazy Bill
Mar 16, 2013, 12:00 PM
I sent another bug report on this, but I'm sure it will get nowhere fast as the last bug report did when 10.8.2 with the slow shut down was submitted. :mad:

Apple FeedBack Link

http://www.apple.com/feedback/

Already submitted. With system logs just like the dozen times before. I think my submissions are getting caught in Apple's SPAM filters by now. This will be the last time I deal with this and I seriously doubt 10.8.4 will address it. The only hope is that the coders working on 10.9 will not recycle these same anomalies and do a bit more "from the ground up" coding. LOL!
:D

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%.

I'm not as fortunate. Early 2011 MBP here. Overall, I'm lucky to get 4 hours of casual use under ML. (Snow Leopard gives me a tad over 5 hours).

As of now, I am entertaining the idea of actually going back to SL (again). I'll sit out OSX 10.9 and by the time 10.10 (ten?) comes out I'm ready for a another machine. A lot depends on how long software developers will keep supporting 10.6. Right now, it's pretty good.

macrem
Mar 16, 2013, 04:58 PM
I think it's an ugly bug & shameful to leave unfixed for so long.

Puevlo
Mar 16, 2013, 06:17 PM
How sad. The hardware gets thinner but the software keeps getting fatter.

kensic
Mar 16, 2013, 08:20 PM
i have done 5 shutdowns, with each shutdown with various usage time (1-6 hours of usage) and it shuts down at 2 secs every time

*crosses fingers* that it will be like this forever

BasicGreatGuy
Mar 16, 2013, 08:37 PM
I installed the update, and have not seen any difference in what I consider to be a long shutdown (17- 20 seconds). 13" MBP late 2011

printz
Mar 17, 2013, 02:32 AM
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
Mar 17, 2013, 06:25 AM
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.

andrezuppe
Mar 17, 2013, 09:39 AM
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

cooky560
Mar 17, 2013, 11:00 AM
It's been there since Lion.


Umm no it hasn't in 10.7 - 10.8.2 I went from a white screen straight to login box. Now theres this silly 3 or 4 second animation where the apple logo moves upwards, before showing the login screen

UBS28
Mar 17, 2013, 11:38 AM
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?

CrystalMeth
Mar 17, 2013, 12:31 PM
Something is wrong with Mountain Lion?

Simon says of course.

andrezuppe
Mar 17, 2013, 02:17 PM
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
Mar 19, 2013, 01:04 AM
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.

Mike MA
Mar 19, 2013, 02:41 AM
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.

It started with 10.8.1, probably even 10.8.

Badagri
Mar 19, 2013, 08:57 PM
10.8.1 was a very small update? I don't think it was anymore than a couple of MB on software update, but it's 24MB. http://support.apple.com/kb/DL1571

Lunchb0x8
Mar 20, 2013, 04:16 AM
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.

justperry
Mar 20, 2013, 05:07 AM
Just plain ridiculous my Powerbook G4 1.67 starts up and shuts down faster than my 2012 Mini, an 8 year old Laptop for ******** sake.

nangariel
Mar 20, 2013, 09:19 AM
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
Mar 20, 2013, 09:24 AM
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
Mar 23, 2013, 12:33 PM
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
Mar 23, 2013, 01:04 PM
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
Mar 23, 2013, 03:00 PM
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
Mar 23, 2013, 03:12 PM
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
Mar 23, 2013, 03:33 PM
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
Mar 23, 2013, 03:58 PM
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
Mar 23, 2013, 04:34 PM
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
Mar 23, 2013, 06:02 PM
You need to do this search in console under /var/log/com.apple.launchd/launchd-shutdown.system.logYes. Thank you for adding that. I forgot. :o


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
Mar 24, 2013, 03:03 PM
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...

BlaqkAudio
Mar 24, 2013, 03:35 PM
Umm no it hasn't in 10.7 - 10.8.2 I went from a white screen straight to login box. Now theres this silly 3 or 4 second animation where the apple logo moves upwards, before showing the login screen
Yes it has: https://www.youtube.com/watch?v=y4Y80hEQjqE

Gogol
Mar 25, 2013, 03:41 AM
You are all complaining about the shutdown times. What about the time it took to investigate and write about this?;)

cooky560
Mar 25, 2013, 05:43 AM
Yes it has: https://www.youtube.com/watch?v=y4Y80hEQjqE

Well thats very strange because with verbose boot enabled I've only seen it since 10.8.3

adnbek
Mar 25, 2013, 05:16 PM
Yes it has: https://www.youtube.com/watch?v=y4Y80hEQjqE

That animation didn't show up on some Macs. I don't know what the cause was but I could tell you that while the Macbook Pros circa 2009 and 2010 showed it, the 2011 did not. It just flashed white, then instant login window. Same for my 2011 Mini.

Other than being different models, I don't know what the cause was. The installations were identical as I was the one who upgraded them all and they were exact duplicates in every way in terms of installation, login items and apps installed.

NJFP
Mar 30, 2013, 09:10 PM
my shutdowns are 4-5 secs.. if you don't have ssd don't expect to get miracle from your computer

Weil, my "miracle" was a 45 sec boot and a 3 sec shut down on Snow Leopard, now it's taking "forever" with ML. IF I wanted to wait that long, I'd have stayed with Winblows.

TennisandMusic
Mar 30, 2013, 11:23 PM
Weil, my "miracle" was a 45 sec boot and a 3 sec shut down on Snow Leopard, now it's taking "forever" with ML. IF I wanted to wait that long, I'd have stayed with Winblows.

Windows shuts down in seconds. :p

justperry
Mar 30, 2013, 11:30 PM
Windows shuts down in seconds. :p

How long does it stay that way.:p

But, I have to agree with the sentiment here, Apple messed up, most if not all former OS versions shut down almost instantly, not so in ML.
Easy fix if you know how but it shouldn't be this way.

th-gates9345
Mar 31, 2013, 04:12 AM
... Easy fix if you know how but it shouldn't be this way.

Please, how can i do this easy fix? Thanks.

justperry
Mar 31, 2013, 04:45 AM
Please, how can i do this easy fix? Thanks.

I recommend you to read this whole thread, the answers are all there, but I recommend you to switch on Verbose Mode, you the can see what is going on after you click restart.
The easiest way to do is to download Onyx, open Onyx, go to the Parameters Tab, next login tab and you'll see a setting in the lower part called startup mode, change to Verbose, if you are done just change it back to normal.
Next startup you will see text upon startup and shutdown, look what is going on on shutdown.
The rest is all here in this thread, happy reading.

macrem
Mar 31, 2013, 04:59 AM
Windows shuts down in seconds. :p
What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.

Krazy Bill
Mar 31, 2013, 10:27 AM
What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.

So no, I can't picture Jobs, Tim Cook or most any other Cupertino exec hunkered over an iMac for very long (if at all) much less using the OSX "Shut Down" command on a networked terminal.

katewes
Mar 31, 2013, 11:29 AM
I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.

To confirm the above, this interview with Tim Cook indicate he uses iPad and iPhone 80% of the time.

http://appleinsider.com/articles/12/12/06/tim-cook-ditched-physical-keyboards-uses-ipad-and-iphone-80-of-the-time

People, think of the significance: if Apple's CEO uses iPad 80% of the time, it means he is not daily experiencing the crap of Mountain Lion that we have to. Tim Cook has no idea of what the people at grassroots are experiencing. It's like a politician who has lost touch with the common people - and keeps parroting the line "Apple makes great products".

This has to be a recipe for long term failure. Surely the graveyard of corporations is littered with companies who are number one in their field for a decade or so, but fell into the gutter by losing touch with its customer base.

macrem
Mar 31, 2013, 11:33 AM
I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.

So no, I can't picture Jobs, Tim Cook or most any other Cupertino exec hunkered over an iMac for very long (if at all) much less using the OSX "Shut Down" command on a networked terminal.
Jobs would not hesitate to phone people on weekends if the background color of an icon was slightly off. This bug affects regular shutdowns. It's one of the basic tests when you put an OS through it's paces (reboot time). Such a regression should not make it past QA.

Badagri
Mar 31, 2013, 05:56 PM
What-a-shame! I think Steve would have already opened up a can of whoopass so this bug would have been fixed long ago.

http://imageshack.us/a/img824/7816/26527478.jpg


I seriously doubt that. The higher up in the executive food chain, the less you'll find these people actually putting products through their paces like we do. Especially when it comes to macs. They simply don't have the time and are most likely tethered to iPads and iPhones for the bulk of their corporate lives.

So no, I can't picture Jobs, Tim Cook or most any other Cupertino exec hunkered over an iMac for very long (if at all) much less using the OSX "Shut Down" command on a networked terminal.

Shutting down a computer is putting it through it's paces? nobody shuts down at Apple?

zakee00
Mar 31, 2013, 11:06 PM
Windows shuts down in seconds. :p

Unless it has updates to install. Then you're looking at like five minutes.

Krazy Bill
Apr 1, 2013, 07:47 AM
nobody shuts down at Apple?Nobody of any consequence. That and given how long this issue has remained in ML... what do you think?

SR45
Apr 1, 2013, 11:03 AM
Please, how can i do this easy fix? Thanks.

In TERMINAL type in below after doing a "Disk Repair Permission" in "Disk Utility" Some may not have done the Disk Repair Permission but it worked for me in doing so and not when I passed on this





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

SR45
Apr 1, 2013, 11:05 AM
Sorry Double post

star trek
Apr 1, 2013, 01:18 PM
In TERMINAL type in below after doing a "Disk Repair Permission" in "Disk Utility" Some may not have done the Disk Repair Permission but it worked for me in doing so and not when I passed on this





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

Thanks SR45 working Good on Imac with Mountain Lion 10.8.3 !!!

1) Repairing permissions

2) The only thing I had to change is : On Terminal doing ----> su Enter password Enter and then Copy and Paste the second line : sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2 and Enter !!!!

Opening Terminal and doing exactly as U write the Terminal doesnt recognize commands !?!? Doing something Wrong !?!? However now Mountain Lion SHUT DOWN AT SPEED OF LIGHT !!!! Many Thks !!!!!

Junkyman
Apr 1, 2013, 11:43 PM
Nobody of any consequence. That and given how long this issue has remained in ML... what do you think?

I totally agree with you. It's a shame this problem has persisted for so long, but I guess it has just escaped the attention of people it would have most mattered for it to be fixed in a timely fashion.

As for the solution found by you guys, splendid. Finally fixed the issue for me. I'm really happy.

And lastly: Don't let yourself get trolled by these morons here in the forum who can't appreciate someone actually finding AND caring about a bug that has been bugging us all - yes, even those who pretend they are so cool and a 20 second shutdown is just the most normal thing in the world everyone should just accept. Some people are just so ignorant.

My respect to you, keep up the good work.

SR45
Apr 2, 2013, 09:26 AM
Thanks SR45 working Good on Imac with Mountain Lion 10.8.3 !!!

1) Repairing permissions

2) The only thing I had to change is : On Terminal doing ----> su Enter password Enter and then Copy and Paste the second line : sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 2 and Enter !!!!

Opening Terminal and doing exactly as U write the Terminal doesnt recognize commands !?!? Doing something Wrong !?!? However now Mountain Lion SHUT DOWN AT SPEED OF LIGHT !!!! Many Thks !!!!!


Forgot to show the enter PASSWORD thingy after first entry in Terminal

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

Press ENTER key after above, which will than ask for PASSWORD. Enter your apple password. Go to next entry. Works for me star trek


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

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

Want to thank you for stating that you can Cut and Paste. Didn't even know that you can do this in Terminal. Saves some work ;) :D

tiger1050
Apr 2, 2013, 09:48 AM
In TERMINAL type in below after doing a "Disk Repair Permission" in "Disk Utility" Some may not have done the Disk Repair Permission but it worked for me in doing so and not when I passed on this

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

Another vote of thanks to SR45, works like a charm 3-4 second shutdown.

Simplicated
Apr 2, 2013, 01:22 PM
10.8.4 beta was released (http://www.macrumors.com/2013/04/01/apple-issues-first-beta-of-os-x-10-8-4-to-appleseed-members/), I would be interested in knowing if this problem has been resolved yet.

saturnotaku
Apr 2, 2013, 08:24 PM
I mentioned this in another thread but uninstalling Steermouse solved my long shutdown times. Perhaps this is an issue related to some sort of third party software.

cocky jeremy
Apr 2, 2013, 11:03 PM
I am truly curious ... why does this matter in the slightest?

It doesn't. People just get OCD about crazy, unimportant stuff.

turtlez
Apr 2, 2013, 11:36 PM
I shut down the other computer with SL and it is pretty much instant off. maybe not even 1 second from mouse up on the shutdown button and off. My new 2013 iMac takes about 20 seconds haha. I very rarely shut down so it doesn't bother me. It will be fixed soon enough I am sure.

w0lf
Apr 2, 2013, 11:41 PM
10.8.4 beta was released (http://www.macrumors.com/2013/04/01/apple-issues-first-beta-of-os-x-10-8-4-to-appleseed-members/), I would be interested in knowing if this problem has been resolved yet.

I still have slow shutdowns with 10.8.4

Badagri
Apr 3, 2013, 11:20 AM
It doesn't. People just get OCD about crazy, unimportant stuff.

Some Mac users can be so amusing at times with their double standards.

Simplicated
Apr 3, 2013, 11:25 AM
It doesn't. People just get OCD about crazy, unimportant stuff.

This is far from unimportant. Imagine how people in a hurry need to pack their Macs (especially on HDD-based Macs) and leave as fast as possible. Plus, shutdown used to be extremely fast on 10.6 and 10.7; there's no reason to settle for less.

trntogl
Apr 3, 2013, 11:30 AM
I have noticed my Imac shuts down faster now with ML 10.8.3.

Interesting, mine has totally SLOWED DOWN when booting up and shutting down since I installed Mountain Lion. I wish I never did it, my computer ran perfectly with Snow Leopard but a friend mentioned Mountain Lion being great and works well with iCloud.

Wavs don't work anymore with new email that I had in Sounds.

I am getting pixels in email window preview....

etc etc etc.

Wish I never installed Mountain Lion.

Think I should trying reinstalling? Was at Apple Store because my iCal was not syncing, they fixed that but said my system worked fine otherwise when doing tests. Really? For those that don't think 40 sec. isn't long, I'm glad for you. When you purchase a costly laptop like Apple, it should work better than that. Why they keep changing things that we had liked previously is beyond me.

One thing that everyone seems to want is alphabetical arranging for favorites, it's been mentioned by everyone... every update they put out, it's not there.

Seems folks that have this slower issue with Mountain Lion have tried several fixes and nothing is working, maybe Apple ought to figure out how to send a fix for it? And there are many folks complaining about it, so not everyone doesn't mind the 30+ seconds it takes. Everyone is entitled to their own ...

Krazy Bill
Apr 3, 2013, 02:01 PM
I still have slow shutdowns with 10.8.4Can you check your console logs to confirm this? (I don't have 10.8.4)

1.) Reboot
2.) Launch the "console" app (use spotlight to find it)
3.) Highlight System Log on the side bar of the console app.
4.) Search for "exit timeout" in the upper-right field.

This will list those daemons that didn't close properly thereby causing the delay: Exit timeout elapsed (20 seconds). Killing

If this issue persists in 10.8.4 I have some thinking to do about continuing to support Apple. Not because I can't live with this bug... mainly because I'm getting uncomfortable with Apple's feedback system, their arrogance in prioritizing bugs and also their general incompetence which will only get worse as they continue to de-emphasize OSX.

Anybody opened an issue in the Apple Bug Reporter since 10.8.3 has been released?I did just in case everybody assumes Apple wasn't informed" but I'm sure my stuff goes to a spam folder by now. No word on duplicate issues.

I'm done reporting now. Besides, all the OSX coders are in the iOS building right now. (All 2 of them).

Mike MA
Apr 3, 2013, 02:06 PM
Anybody opened an issue in the Apple Bug Reporter since 10.8.3 has been released? Are the bugs still being closed as duplicates?

I'm actually tired of uploading logs since last December...

w0lf
Apr 3, 2013, 03:39 PM
Can you check your console logs to confirm this? (I don't have 10.8.4)

http://i.imgur.com/81DElDW.png

Badagri
Apr 3, 2013, 04:29 PM
there's no reason to settle for less.

There is if you have double standards like, cocky jeremy.

Krazy Bill
Apr 3, 2013, 05:11 PM
<image snipped>

Well, crap. Un-freaking-believable. :(

Thanks for taking the time to post a screen shot.

Lunchb0x8
Apr 3, 2013, 11:41 PM
Well, since I posted my fixes, I have updated to 10.8.4 beta, after doing a clean reinstall to fix some other issues I was having.

I am going to have to reapply my fixes for now, but I am not too impressed with waiting longer for my computer to shut down than it takes to start it, open this thread and reply.

I shut down after use, because I don't always know when I am going to use it next, and also, even the minimal power in sleep is still power, so if my MBA somehow gets wet in my travels, I don't want to have to think "OH NO, shut down quickly", then wait 20 seconds, during which my computer could be frying its internals.

Simplicated
Apr 4, 2013, 03:51 AM
Umm no it hasn't in 10.7 - 10.8.2 I went from a white screen straight to login box. Now theres this silly 3 or 4 second animation where the apple logo moves upwards, before showing the login screen

It has. But it only comes up sporadically and I don't know why. Looks like they fixed it in 10.8.3.

adnbek
Apr 4, 2013, 06:46 AM
Can you check your console logs to confirm this? (I don't have 10.8.4)

1.) Reboot
2.) Launch the "console" app (use spotlight to find it)
3.) Highlight System Log on the side bar of the console app.
4.) Search for "exit timeout" in the upper-right field.


It's not under system.log Krazy Bill. We talked about this before. It's here:

Krazy Bill
Apr 4, 2013, 08:21 AM
It's not under system.log Krazy Bill. We talked about this before. It's here:Yes, I know. I just didn't want to instruct people to "drill down" through the menu.

adnbek
Apr 4, 2013, 09:32 AM
Yes, I know. I just didn't want to instruct people to "drill down" through the menu.

Yes but system.log shows timeouts that are unrelated to shut down. Timeouts can occur at other times too while the system is running and have nothing to do with hanging reboots/shut downs.

Badagri
Apr 4, 2013, 12:01 PM
I'm getting the same as, adnbek. Nothing else is timing out except apple services. Plus I've read a lot of articles on this recently. It's only a 90% fix. Hence I'm not tampering.

Mike MA
Apr 5, 2013, 10:51 AM
Besides, all the OSX coders are in the iOS building right now. (All 2 of them).

Well, I'm hoping Gruber is wrong on that one.

What bothers me is the actual consequence if true. Both OS X and iOS should be redesigned as anounced by Tim - but as soon as capacities are rare people are pulled from the OS X to support the mobile team. Should sell my Macs und finally get some iPads. Welcome to the future.

Mike MA
May 2, 2013, 03:05 PM
I did just in case everybody assumes Apple wasn't informed" but I'm sure my stuff goes to a spam folder by now. No word on duplicate issues.

This is what my ticket shows which was closed as a duplicate - the original one unsurprisingly still is....open....

ultraspiracle
Jul 11, 2013, 08:06 PM
This is what my ticket shows which was closed as a duplicate - the original one unsurprisingly still is....open....

Very interesting - exactly what they did with another one I know of.