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

OS X 10.8.4 Build 12E52 Seeded to Developers

dastinger said:
FFS, please understand this once and for all. Pull your heads out your ass and understand that it's not about shut down being faster because we want it to be. It's about a bunch of processes that fail to quit ALL THE TIME so they need to be killed. How isn't that important, easy to diagnose and probably to fix? Let's applaud Apple for ignoring it and instead care about Safari being snappier? Good God.
Click to expand...

I'm not sure if you responded to the wrong post or didn't read what I wrote, but you're agreeing with me.

People don't like to hear the complaints, but they will stop when Apple fixes the problem. Anyone who doesn't want to hear them any more, drop Apple a line bugging them to fix it.
 
Macrolido said:
Only six betas to go...
Click to expand...


Wow fellas. It looks like just maybe the much yawned over "Safari iz teh snappier! hehehehehehehe" finally got old for the Mac dorks, and they moved onto this for their kicks instead. It only took them 9 years!

I feel we're witnessing the dawn of the Anti-ADHD era. Instead of being bored of something after 5 minutes, they get more and more into it week after week, month after month. I fear it could spiral out of control into a dangerous and unstoppable chain reaction. Then the AADHD Mac Dorks will start spontaneously combusting.
Then their dorky friends can send dorky tweets about how they saw the throbbing dorky giblets of their self detonated dorky comrade.

But heres a little something so the AADHD Mac dorks don't get upset or offended.

lulz xd wut idk o0 ^^ SNAPPEH!!

See, you just gotta reach out to them in their own language. However retarded it may look to those of us who did get at least a half decent education and are able to string together a coherent sentence.

:cool:
 
RedGeminiPA said:
I agree. If shutdown time is so important because of Bootcamp, install a damn VM and be done with it. I use VirtualBox, and it works just fine for FREE. It's also a lot more flexible.
Click to expand...

Yeah, because performance is meaningless ... or maybe you think that people aren't going to Windows to do things that take a lot of resources. Which is it?
 
thomaskc said:
I wonder how every thread on this forum turns into shutdown times every single time.... no matter the initial topic!

It's boring people.. come up with something new please.
Click to expand...

The solution is simple. Every time a new beta will be released, we know someone who experiences the shutdown problem will ask if the current beta has fixed it. That's normal and expected. Instead of people replying with countless useless attempts to tell that person why he shouldn't care about shutdowns or how they themselves never shutdown etc, just answer: "fixed" or "not fixed", and move on. That will keep everything short and sweet. But for some reason people always feel the need to incite controversy by telling those who care about this bug that they shouldn't care about it, and that will go nowhere and just derail more and more threads.
 
JohnDoe98 said:
The solution is simple. Every time a new beta will be released, we know someone who experiences the shutdown problem will ask if the current beta has fixed it. That's normal and expected. Instead of people replying with countless useless attempts to tell that person why he shouldn't care about shutdowns or how they themselves never shutdown etc, just answer: "fixed" or "not fixed", and move on. That will keep everything short and sweet. But for some reason people always feel the need to incite controversy by telling those who care about this bug that they shouldn't care about it, and that will go nowhere and just derail more and more threads.
Click to expand...

Dont get me wrong, people are allowed to have their problems and things they want fixed, by all means, different things piss off different people. But I am just tired of browsing through page after page with useless information from people that clearly have 0 actual stats, recordings or insight knowledge to both how things work or if anything has actually changed over the last 3 years. I wouldn't mind the topic if there was actual data, some juice to get hooked on, as of right now its just hot air floating around for no reason.

Anyway /rant

Must be time for a new beta soon? :p
 
milo said:
I'm not sure if you responded to the wrong post or didn't read what I wrote, but you're agreeing with me.

People don't like to hear the complaints, but they will stop when Apple fixes the problem. Anyone who doesn't want to hear them any more, drop Apple a line bugging them to fix it.
Click to expand...
Sorry, it was misleading. When I said "please understand this" I was referring to what you said in your post. Yes, I was agreeing with you.
 
thomaskc said:
I wouldn't mind the topic if there was actual data, some juice to get hooked on, as of right now its just hot air floating around for no reason.
Click to expand...

We've provided hard data in other threads. There are well documented console logs pinpointing the problem to a few, specific, processes. That's why it is so annoying and futile when people claim there is no issue and we shouldn't care. If anyone is actually interested in finding out what the problem is it won't be hard for them. I don't see the need to constantly post that data in each thread. However if someone says there isn't a problem, I don't see the harm in informing them otherwise.
 
JohnDoe98 said:
However if someone says there isn't a problem, I don't see the harm in informing them otherwise.
Click to expand...
One of the reasons why this kind of debate continues is that some people become irritated when posts on an issue suggest the problem is universal when it is clearly not. Probably only being experienced by a few.
(I'm not saying you are guilty of that, just making a general comment.)
 
I feel it's an issue still worth mentioning because OSX used to shut down fairly quickly and now it doesn't for many. I have a 2007 White Macbook with 10.6.8 that boots up and shuts down quicker than my 2011 MBP, even with a clean install. Sometimes it does shut down quick in ML, but most of the time I get the spinning thing on the gray screen and it takes a bit.
 
imacken said:
...suggest the problem is universal when it is clearly not. Probably only being experienced by a few.
Click to expand...

While it's probably not "universal", meaning literally every mac has a noticeable problem with it, it certainly seems to be very common. Just because you don't see the problem doesn't mean that only a few people have the issue.
 
Luap said:
Wow fellas. It looks like just maybe the much yawned over "Safari iz teh snappier! hehehehehehehe" finally got old for the Mac dorks, and they moved onto this for their kicks instead. It only took them 9 years!

I feel we're witnessing the dawn of the Anti-ADHD era. Instead of being bored of something after 5 minutes, they get more and more into it week after week, month after month. I fear it could spiral out of control into a dangerous and unstoppable chain reaction. Then the AADHD Mac Dorks will start spontaneously combusting.
Then their dorky friends can send dorky tweets about how they saw the throbbing dorky giblets of their self detonated dorky comrade.

But heres a little something so the AADHD Mac dorks don't get upset or offended.

lulz xd wut idk o0 ^^ SNAPPEH!!

See, you just gotta reach out to them in their own language. However retarded it may look to those of us who did get at least a half decent education and are able to string together a coherent sentence.

:cool:
Click to expand...

Wow! Apply cold water to that burn!
 
cmChimera said:
...Again, your problems aren't representative of most people. I run OS X weeks and months at a time without shut down and it runs perfectly. You may want to look at what's wrong with your set up...
Click to expand...
Never said they were representative.

Whats wrong with my set-up, primarily, is having moved from Snow Leopard to Mountain Lion. In 44 years of IT use, Mountain Lion is close to top (almost certainly in the top one as I can't think of another candidate) of the least reliable software I've ever seen.

Status:
1. All software, Crab-Apple and 3rd party is absolutely latest version, all update options report no updates
2. All worked 'perfectly' under Snow Leopard (I skipped Lion), though I concede that all have been updated since to the Mountain Lion compatible version
3. Disk Utility reports no errors on any disk, no permissions errors
4. When Time Machine not active/not been manually stopped most things sort of work
5. No 'edits'/'adjustments' by tinker tool etc. other than using tmutil to set the attributes on one specific (40gb) file
6. Rig has several external disks and I think its these that are not the issue for 'most' users.

Examples of issues:
A. Time Machine has been 'Preparing backup' for the last two hours - opened Disk Utility an hour ago; its still 'Gathering Information' - Hmmm... feels like deadly embrace to me
B. Earlier today - Used iPhoto for a few minutes, didn't close it then and there. Later, closed it, window disappeared almost immediately. An hour later, process still hanging around 'Not responding'. Force quit, re-open and it won't start as disk / library is locked so restart needed if I want to use it again.

IMHO; Apple, doesn't test anything well; in particular hasn't thought recently about what happens when drives sleep. Of course, drives on phones are rarely in sleep mode
 
dastinger said:
FFS, please understand this once and for all. Pull your heads out your ass and understand that it's not about shut down being faster because we want it to be. It's about a bunch of processes that fail to quit ALL THE TIME so they need to be killed. How isn't that important, easy to diagnose and probably to fix? Let's applaud Apple for ignoring it and instead care about Safari being snappier? Good God.
Click to expand...
No let's applaud you ranting about something you clearly have no understanding about. As if tracing a problem can be done in a few seconds, solving it can be done in a few more seconds, some testing in yet another few seconds and doing that circle all over again a couple of times in no more than 1 minute! You lack all reality in this.

What you see are symptoms. Symptoms might be the problem itself, it may be just the outcome of several problems. Finding what is going on will take some time. Sometimes you'll find it in minutes, most of the time it takes days, weeks and with complex problems even months. Fixing the problem would be exactly the same: it can take a few minutes, days, weeks or even months depending on how complex it is. The reason for this is very simple: you need to reproduce it to make sure that whatever you identified as the problem really is the problem. The same applies to the solution: you need to make sure it really is the solution. If not you get the Microsoft craziness: a patch for a patch that patches a patch. Quality takes time.

If takes a long time it might mean they are not caring that much, it might also mean that they are having difficulty in finding and/or resolving the problem. There is no way you can tell which one it is so it's stupid to say they are not caring (as it is as saying they are taking their time to get it resolved properly).

So what makes you say the cause is stuff not shutting down, it's easy to diagnose and Apple is not caring? All I see are random assumptions you are making without having any knowledge about software development and standard troubleshooting.
 
dyn said:
As if tracing a problem can be done in a few seconds, solving it can be done in a few more seconds, some testing in yet another few seconds and doing that circle all over again a couple of times in no more than 1 minute!
Click to expand...

Who is asking for a fix in one minute? In case you're forgotten, 10.8.0 shipped last July. If that's not enough time for Apple to fix it, they either don't care about the problem, or they lack the skills to fix it. As you pointed out, we don't know which of those two possibilities is the case, but neither one makes Apple look good.
 
dyn said:
No let's applaud you ranting about something you clearly have no understanding about. As if tracing a problem can be done in a few seconds, solving it can be done in a few more seconds, some testing in yet another few seconds and doing that circle all over again a couple of times in no more than 1 minute! You lack all reality in this.

What you see are symptoms. Symptoms might be the problem itself, it may be just the outcome of several problems. Finding what is going on will take some time. Sometimes you'll find it in minutes, most of the time it takes days, weeks and with complex problems even months. Fixing the problem would be exactly the same: it can take a few minutes, days, weeks or even months depending on how complex it is. The reason for this is very simple: you need to reproduce it to make sure that whatever you identified as the problem really is the problem. The same applies to the solution: you need to make sure it really is the solution. If not you get the Microsoft craziness: a patch for a patch that patches a patch. Quality takes time.

If takes a long time it might mean they are not caring that much, it might also mean that they are having difficulty in finding and/or resolving the problem. There is no way you can tell which one it is so it's stupid to say they are not caring (as it is as saying they are taking their time to get it resolved properly).

So what makes you say the cause is stuff not shutting down, it's easy to diagnose and Apple is not caring? All I see are random assumptions you are making without having any knowledge about software development and standard troubleshooting.
Click to expand...
Are you serious? Do you even know for how much time the problem exists? Have you been reading the forums? How many persons here said they can replicate the issue EVERY TIME and EVERY TIME the issue is with the same processes that fail to quit during shut down?

This is exactly the same as the issue with reduced performance on 15" rMBPs. It was there since forever but Apple only cared to fix it once people started seriously complaining. Once that happened, Apple took 15 days to solve the issue by updating the EFI. Maybe they were testing it for months. Or maybe the timing was a mere coincidence :rolleyes:
 
Last edited:
w0lf said:
Isn't that the same exact amount as osx?

1) Move mouse to corner
2) Click on Apple
3) Click on Shutdown
4) Click on Confirm

If there was a default way to shut down in two mouse clicks from anywhere there'd probably be a whole lot of cases of people randomly shutting down their computers.
Click to expand...


Actualy it's more like this:

1. Move pointer to the Apple menu.
2. Hold down the mouse and move to 'Shutdown'.
3. Click on 'Shutdown'.


Hugh
 
OS X 10.8.4 Build 12E52 Seeded to Developers

geralddarden said:
Anyone with an Nvidia based MBP (mid-2010) tried this build? If so, does it solve the random KPs?
Click to expand...

Sorry, the only topic discussed in this thread is slow shutdown times which makes this thread absolutely useless to discuss 10.8.4 beta releases. If you want any actual information on 10.8.4 betas, looks like you need to start a different thread.

I have a 2012 rMPB and don't have random KPs.
 
Last edited:
geralddarden said:
Anyone with an Nvidia based MBP (mid-2010) tried this build? If so, does it solve the random KPs?
Click to expand...

I think you probably have a problem with your computer.

I've been using the MacBook Pro (13-inch, Mid 2010) 7,1 with all the latest builds, not once have I experienced a kernel panic. I'm pretty sure if random kernel panics were being caused by a build of 10.8 on Nvidia macbook pros from 2010 you wouldn't be the only person I've heard complain about it.
 
w0lf said:
I've been using the MacBook Pro (13-inch, Mid 2010) 7,1 with all the latest builds, not once have I experienced a kernel panic. I'm pretty sure if random kernel panics were being caused by a build of 10.8 on Nvidia macbook pros from 2010 you wouldn't be the only person I've heard complain about it.
Click to expand...

I think the problems with KPs affected Core i5/i7 models, not the Core2Duo 13-inch.
 
milo said:
People aren't asking for a "feature", people are asking for a bug to be fixed.



Maybe you still can, just hold down F12 instead of eject.
Click to expand...

Nope, standard function for the f keys are not supported unless you have a apple keyboard.
 
I don't want to get everybody's hopes up, but I'm getting awesome WiFi stability. No more random disconnects. Anybody else is having same results?

Otherwise, can't tell difference between earlier betas nor 10.8.3.
 
Ddyracer said:
Nope, standard function for the f keys are not supported unless you have a apple keyboard.
Click to expand...

Did you try it? Works with my mac mini and a windows keyboard. But that's with 10.6, maybe they took it out in 10.7 or 10.8.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back