Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Slow shutdowns are usually there for a reason. When you ask the system to shutdown, it politely asks running processes to terminate. There are very many reasons why an individual process may not respond to a shutdown request in a short time. You would not thank your computer, for example, if it powered off with half a file written to your filing system. Hardware problems, as well as software and networking problems, can cause slow shutdowns.

If you use Google you will probably find guidance that you can use to go through the system events that take place during shutdown. There may be some clue there as to why your particular device is taking its time. If you raised a help call with Apple, they would probably ask you to provide the event log.

Yeah, but why the sudden since 10.8.X, it was never there in the past and I have never had any data loss as a result of the excellent fast shut down. Now they are telling you to wait for 2 minutes; sounds more like a lame excuse to me......
 
Yeah, but why the sudden since 10.8.X, it was never there in the past and I have never had any data loss as a result of the excellent fast shut down. Now they are telling you to wait for 2 minutes; sounds more like a lame excuse to me......

If you follow the advice given, you may be able to find out why. It won't be happening for no reason. My flaky drive was "never there in the past". My WiFi dropouts were "never there in the past". The "Phone Home" software I installed that ticks away in the background was "never there in the past" etc.

The tools are there for you to find out what is happening during shutdown. I'm not going to do it for you. I suggest you do some research rather than expect something to happen by magic.
 
If you follow the advice given, you may be able to find out why. It won't be happening for no reason. My flaky drive was "never there in the past". My WiFi dropouts were "never there in the past". The "Phone Home" software I installed that ticks away in the background was "never there in the past" etc.

The tools are there for you to find out what is happening during shutdown. I'm not going to do it for you. I suggest you do some research rather than expect something to happen by magic.

Excellent post. There is a psychological phenomenon that people suffer from after updates or upgrades. After 30 plus years fixing Apple equipment I have lost count of the times people suddenly 'observe' something they perceive as 'caused' by 'changes'. Two come to mind. One guy's color monitor went black and white ... he had never had a color monitor (this on an Apple ][), and only yesterday after upgrading a woman's Mac to Mountain Lion she insisted her iPad would no longer send SMS messages ('which it had always been able to do'). There should be a specific medical name for these mental conditions ... LOL
 
It won't be happening for no reason.

The reason is because Apple messed up shutdown in 10.8 (or was it 10.7 and still continuing?). There's nothing to research or troubleshoot, this is a universal problem. It's probably worse for some people than others, but virtually every user has slower shutdowns than with 10.6. And it's not a perception issue, it's easy enough to time how long it takes to shut down, and it's measurably much longer on 10.8 than 10.6.

I suggest you do some research before posting an answer that's nothing more than an uninformed gut reaction.
 
The reason is because Apple messed up shutdown in 10.8 (or was it 10.7 and still continuing?). There's nothing to research or troubleshoot, this is a universal problem. It's probably worse for some people than others, but virtually every user has slower shutdowns than with 10.6. And it's not a perception issue, it's easy enough to time how long it takes to shut down, and it's measurably much longer on 10.8 than 10.6.

I suggest you do some research before posting an answer that's nothing more than an uninformed gut reaction.

Rubbish. It's not a universal problem. People with slow shutdowns will complain about it, and those without will not. The former are a vocal minority. If, for any reason, later builds do happen to be slower, have you considered for a moment that there might well be a very good reason for it? A reason that is not related to impatience?

At the risk of repeating myself, there are tools available to see exactly what your machine is up to when it shuts down. Such logs are there to cater for users who have problems with their setup. If you can be bothered to look into it. Which I can't, because my laptop shuts down lickety-split, thank you very much.
 
The reason is because Apple messed up shutdown in 10.8 (or was it 10.7 and still continuing?). There's nothing to research or troubleshoot, this is a universal problem. It's probably worse for some people than others, but virtually every user has slower shutdowns than with 10.6. And it's not a perception issue, it's easy enough to time how long it takes to shut down, and it's measurably much longer on 10.8 than 10.6.

I suggest you do some research before posting an answer that's nothing more than an uninformed gut reaction.

Weird, when I do a clean install... shutdowns are fast. Once I load up all the services and apps I use, only then do things change. Seems like a user issue and not an OS issue.
 
It's not a universal problem.

Rubbish. Go look at the apple support boards, it's one of the most widespread things going on with OSX right now. Even if you're happy with the shutdown speed on your mac under 10.8, you can't say there's not an issue unless you've compared it to 10.6 and verified that it isn't any slower.


Weird, when I do a clean install... shutdowns are fast. Once I load up all the services and apps I use, only then do things change. Seems like a user issue and not an OS issue.

If the only way to avoid slower shutdowns is to not install or run any apps, that sure sounds like a universal issue as opposed to a user one.
 
Even if you're happy with the shutdown speed on your mac under 10.8, you can't say there's not an issue unless you've compared it to 10.6 and verified that it isn't any slower.

If the only way to avoid slower shutdowns is to not install or run any apps, that sure sounds like a universal issue as opposed to a user one.

Yes I can. I did have 10.6, and going to 10.8 has not affected my machine in any noticeable way. Neither has it done so for numerous people I know personally who run 10.8 across a variety of machine types. Ergo, it's not a universal problem. If it were, I and the people I know would have it.

The poster to whom you responded has not identified the particular process that is causing an issue on his computer. But it does seem to be an application-related matter in his case rather than an OS issue.
 
If you use Google you will probably find guidance that you can use to go through the system events that take place during shutdown.
Another newbie to the shut down "bug". Take your own advice and search the MR threads about it.

If you raised a help call with Apple, they would probably ask you to provide the event log.
We've been doing this for months. :eek:
 
Does this version cache pages correctly? For example, visit the following site, which marks its home page as having a 30-minute expiry.

http://www.theregister.co.uk/

Enable Developer tools: Safari | Preferences | Advanced | Show Develop Menu in menu bar.

Go to the menu bar and choose Develop | Show Page Resources

On the LHS of the tools section, click www.theregister.co.uk.

On the RHS of the tools section, expand Request & Response.

Click the vulture icon near the top of the web page to reload the home page a couple of times. Request & Response should indicate "Cached Yes".

In version 6.0.4, it indicates "Cached No", which is incorrect. This particular site clearly sets response headers that give the page a life of 1800 seconds (expand the Response Headers section). And yet Safari doesn't seem to put it in the cache. That means an unnecessary and slow reload from the internet each time this kind of page is requested.

Cached is set to no.
 
My Thinkpad T400 (with W7) shutsdown MUCH slower than my MBP (with 10.8.3) and MBA (with 10.8.4).

Frankly I find the T400 slowness more frustrating than the MBP or MBA.
 
Another newbie to the shut down "bug". Take your own advice and search the MR threads about it.

We've been doing this for months. :eek:

Must admit that I'm not sure if it really is a bug or that Apple has made 10.8 do "something extra" during the shutdown sequence.

The slower shutdown feels like 10.8 is doing some simple maintenance to the hard drives orso. Or something like doing a short update of the Spotlight index...?

After installing a fresh 10.8.3 on a Mac Pro and on a Mac mini with SSD the slowish shutdown exist there too. They don't take annoyingly long, but they're clearly longer than before 10.8.

IMHO, might not be a bug, but a feature... :eek:
 
The slow shutdown bug (or feature) is most definitely legitimate issue. Sure, perhaps it is caused by a combination of user software and 10.8, but nonetheless it is present on many systems where it did not previously exist.

In my case, my 2012 15" rMBP with SSD on 10.8 shuts down much slower than my 2011 13" cMBP with a regular hard disk did through 10.6 - 10.7.
 
The slow shut down is defiantly a global problem. I have/had the problem, (I can't remember if 10.8.3 fixed it and I rarely shut down anyway) but it was usually accompanied by a file appearing in your trash when you next boot up.
 
Must admit that I'm not sure if it really is a bug or that Apple has made 10.8 do "something extra" during the shutdown sequence.

The slower shutdown feels like 10.8 is doing some simple maintenance to the hard drives orso. Or something like doing a short update of the Spotlight index...?

After installing a fresh 10.8.3 on a Mac Pro and on a Mac mini with SSD the slowish shutdown exist there too. They don't take annoyingly long, but they're clearly longer than before 10.8.

IMHO, might not be a bug, but a feature... :eek:

Except for the small fact that the console logs show that Apple processes' have failed to shutdown during the exit time out interval, requiring the OS to force quit them, i.e. to "kill them" as the logs report. In other, more simple, words: the computer isn't shutting down the processes properly. This isn't a feature and has nothing to do with maintenance, spotlight, third party apps, etc. The OS has asked those system processes to shutdown and they haven't responded, and thus they ended up being "killed" by the OS, meaning whatever it was they were doing it was cut off before finishing.

The only reasonable explanation I've seen is that there is some bug causing a few of these processes not to respond and it requires fixing. This doesn't have to do with restoring apps, auto-saving, etc. as is evidenced by the fact that even though the system force quit those processes, none of those features not present in 10.6 are adversely affected. Many of us have changed the time out interval to quicken the process with no noticeable differences. In other words, we kill the process after 1 second rather than 20. Apple has it at 20 seconds to make sure if the process does respond, it'll have time to close properly. But that isn't happening anyway.
 
Last edited:
It's time apple put some magic seeds up their anal to produce more updates. What the heck is up with apple these days? ....cook....
 
It's time apple put some magic seeds up their anal to produce more updates. What the heck is up with apple these days? ....cook....

Yeah, you'd think that there was 10.8.1, 10.8.2, two supplemental updates to 10.8.2, 10.8.3, and now 10.8.4 being tested.

That's only 6 updates in less than a year. They should be up to 10.8.18 or something by now.

:rolleyes:
 
Yeah, you'd think that there was 10.8.1, 10.8.2, two supplemental updates to 10.8.2, 10.8.3, and now 10.8.4 being tested.

That's only 6 updates in less than a year. They should be up to 10.8.18 or something by now.

:rolleyes:

Or conversely, you'd think after 6 updates everything would be silky smooth. How bad of a state was 10.8 to begin with? I guess we should be highly enthusiastic that 10.9 might be somewhat functional 6 updates after it's initial release?
 
LOL. People are actually arguing that there isn't a "slow shutdown issue"? Whether you think it's an issue or not, it exists and not a perception thing. There are a few threads about doing stuff in terminal that will make Mountain Lion shut down like it did in Snow Leopard. There are also threads where people are suggesting that the OS is doing some background processes (iCloud related?) which is causing the spinning gear before actually shutting down.

I haven't really read those threads because I don't have a problem with the length of the shutdown since a rarely shutdown anyway, but they do exist.
 
LOL. People are actually arguing that there isn't a "slow shutdown issue"?

No, I don't believe anyone has suggested that. What has been suggested is that it is a 'universal' problem. Which it clearly isn't.
 
No, I don't believe anyone has suggested that. What has been suggested is that it is a 'universal' problem. Which it clearly isn't.

Of the 8 Macs in the family and the 4 from friends, all 12 have this shutdown issue where it goes to a white screen with the spinning gear before actually shutting down. I've also experienced this with a clean install so between all 12 Macs and a clean install, this happens, it's safe to say it's something to do with the OS.

I'm not going to sit here and say that this "issue" is universal because that would be assuming 100% of all Lion or Mountain Lion users would have this problem, I would have no way of determining this but based on the 12 I've seen do this and the numerous threads here and on the Apple Support forums, there is a significant amount so while it's unknown if 100% have this issue, it's there.

If you get a white screen with the spinning gear before it actually shuts down, you have this "issue". Is this intended? No one knows but Apple, but it's definitely not the same as Snow Leopard where the shutdown would be instantaneous after the desktop disappears.
 
No, I don't believe anyone has suggested that. What has been suggested is that it is a 'universal' problem. Which it clearly isn't.

And more importantly what annoys someone doesn't mean that it is a bug. When I shut down my computer I some times find it fast and other times I find it slow - things are occurring in the background but it seems that there are people here who deliberately ignore genuinely useful posts in favour of continuually whining because they like the sound of their own voice. Yes the slow shut down does occur but there is a reason for that - it isn't a bug, it is operating as it was designed.
 
Last edited by a moderator:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.