Apple today issued build 12E40 of OS X Mountain Lion to developers, a week after build 12E36 was released. Build 12E40 marks the fifth beta iteration of OS X 10.8.4.
Apple continues to ask developers to focus on Wi-Fi, Graphics Drivers, and Safari.
The update is available through the software update tool in the Mac App Store and Apple's Developer Page.
Top Rated Comments
10.3 & 10.4? Panther and Tiger? ;)
Pay $100. You get all the magic seeds.
It seems like it's a bit late to be complaining about Panther and Tiger if you ask me.
Why does Apple kill the processes at 20 seconds rather than let them "take as long as they need in order to shutdown properly"? Here's a hint, because if a process or app has hung, it might never shut down properly without the OS force quitting it. Apple figures 20 seconds is a reasonable time to wait for a response before killing it.
Now, if your console log shows that every single time you shutdown certain tasks are crashing and requiring them to be killed, then waiting 19 extra seconds is useless since the records show they will not respond within the given time interval anyway.
I'm all for letting systems take as long as they need to shut down properly, and that is exactly why I'd like Apple to fix things so when I open up my console there are no error logs. Then we wouldn't have cause to complain about slow shutdowns because the system is doing whatever it is supposed to do. But when there are error logs pointing to specific tasks that are not shutting down properly, and the slow response has been shown to be caused by those specific tasks, you can't tell me there isn't something wrong with them and that everything is normal. Error logs are not "normal" behavior, they are there to help diagnose a problem.
We've been doing this for months. :eek:
OK, you win. "Universal" means it happens on 100% of machines, which may not be the case. It's probably not literally "universal", more like extremely widespread. Still definitely a problem with the OS and not user specific though.
People have actually tracked what the system is doing during shutdown, and things are just hanging and the system gives them time to end before finally killing them off. Nothing useful is happening during that time, it most certainly is a bug. And by your logic, when 10.6 shuts down dramatically faster, are you saying there's something wrong with that? Or somehow both a 4 second and a 20 second shutdown are both "as designed" even though there's no advantage to the slower one?
Read the post from johndoe above.
Fixed that for you.