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

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,530
39,366



Apple today seeded build 12D76 of OS X Mountain Lion to developers, marking the twelfth beta iteration of the newest version of Mountain Lion. 10.8.3 was first seeded to developers in November of 2012.

1083.jpg

Build 12D76 comes less than a week after build 12D74 and features no listed changes. Registered developers can download the update on Apple's Developer Page.

Update: We've heard that Apple has seeded this version of OS X 10.8.3 to employees, suggesting that it is the final version of the software and is likely to be released to the public in the very near future.

This post originally referred to Build 12D76 as the thirteenth developer seed of OS X 10.8.3 when it was actually the twelfth seed.

Article Link: Apple Seeds Build 12D76 of OS X Beta 10.8.3 to Developers
 
You have to wonder if Apple is preparing 10.8.3 to be last major update to Mountain Lion.

It's time to introduce 10.9.
 
Leaving aside the pathological desire to update any and all software constantly, I consider thoroughly tested software fundamentally better.

So if Apple really is hammering 10.8.3 this hard to make sure it's clean, I consider that a good thing.

(One could of course argue that they should just let it loose and fix the remaining issues in 10.8.4, but are there any bugs that 10.8.3 is fixing that are so egregious that it needs to come out NOW, thorough testing be damned?)

Does this hold the record for longest run between point iterations of a current-version OSX, though? It's certainly the most betas with no known issues I can remember seeing.
 
Slow shutdown was fixed for me with this build. Anyone else experiencing this?
 
I would have to guess they have all hands working on iOS now, and OS X has been placed on the back burner.
 
Testing is the part of software development which simply needs its time. You can't simply halve its duration by just doubling the resources assigned to it.

Personally I hope that this will fix my issue with USB 3.0 drives which get unmounted as soon as I put my MBA into sleep mode. Time Machine during Powernap still works but I get a warning message every time I wake the device.
Despite this I don't see any other problems with 10.8.2 on my device and Apple should take all the time it needs to stabilize the next update.
 
This is the beta that never ends. This time last year, Mountain Lion beta 1 was already seeded to developers.
 
Leaving aside the pathological desire to update any and all software constantly, I consider thoroughly tested software fundamentally better.

So if Apple really is hammering 10.8.3 this hard to make sure it's clean, I consider that a good thing.

I generally agree with this but considering none of the builds I've tried have added any noticeable bugs I don't think it would have hurt for Apple to have released some sort of update earlier to adress some of the more pertinent issues.

I have to say though, on both computers I have running 10.8.3 I haven't really ran into any problems at all in quite a while (aside from the fact that safari still leaks huge amounts memory after extended usage but I don't really use safari so I don't care).

One could of course argue that they should just let it loose and fix the remaining issues in 10.8.4, but are there any bugs that 10.8.3 is fixing that are so egregious that it needs to come out NOW, thorough testing be damned?

I think a lot of rMBP users are having graphics/lag related issues as well as wifi connectivity issues which I would classify both as being pretty serious. I know that if I was experiencing those sorts of problems for months on end without a fix it would certainly turn me off of wanting to buy another product from the same company especially considering the price of rMBPs.

Does this hold the record for longest run between point iterations of a current-version OSX, though? It's certainly the most betas with no known issues I can remember seeing.

Here's something useless for you :)

The time in days between OS X updates, here's the top 10, not including betas of any kind.

1. 165 days, 10.4.8 - 10.4.9
2. 148 days, 10.5.6 - 10.5.7
3. 148 days, 10.6.4 - 10.6.5
4. 148 days so far,10.8.2SU - 10.8.3
5. 147 days, 10.4.10 - 10.4.11
6. 140, 10.6.2 - 10.6.3
7. 133, 10.7.4 - 10.7.5
8. 112 10.7.2 - 10.7.3
9. 111, 10.4.2 -10.4.3
10. 107, 10.5.2 - 10.5.3

You can see the 10.x.2 - 10.x.3 is one of the longest cycles.

If you go by the original 10.8.2, not the supplemental update, it's been 163 days.

^ 2/28/13 so add 5 days to the total

According to this quote from the 12D68 thread it still isn't the longest yet but it's #2 now and will probably take the #1 spot unless this the GM and it's released this week or something.
 
I got this from member "Sky Blue" here:
https://forums.macrumors.com/threads/1543159/

"The time in days between OS X updates, here's the top 10, not including betas of any kind.

1. 165 days, 10.4.8 - 10.4.9
2. 153 days so far,10.8.2SU - 10.8.3
3. 148 days, 10.5.6 - 10.5.7
4. 148 days, 10.6.4 - 10.6.5
5. 147 days, 10.4.10 - 10.4.11
6. 140, 10.6.2 - 10.6.3
7. 133, 10.7.4 - 10.7.5
8. 112 10.7.2 - 10.7.3
9. 111, 10.4.2 -10.4.3
10. 107, 10.5.2 - 10.5.3

You can see the 10.x.2 - 10.x.3 is one of the longest cycles.

If you go by the original 10.8.2, not the supplemental update, it's been 168 days."

(I've updated the 10.8.2 calculations based on the days that have passed since then).

Edit - w0lf beat me to it.
 
Can I PLEASE just have the fix to the Mac Mini HDMI graphics?

EXACTLY! The 'crushed whites' problem seems to be fixed in the betas for months now. I can remember having a similar problem in 10.5 where OSX recognized my monitor as a TV and therefor produced the screen resolution 1900x1080 instead of 1900x1200. A fix for this was released by Apple 2 weeks later and they didn't wait for the next 10.5.x update.

This time the basic problem seems also to be that OSX recognizes some monitors as TVs. But I just can't get behind why Apple doesn't fix such an issue with a small separate update, so annoying...
 
You have to wonder if Apple is preparing 10.8.3 to be last major update to Mountain Lion.

It's time to introduce 10.9.

In that case I should probably report an issue where the App Store won't authenticate if you remove the first Ethernet card. At the time, 10.8.3 looked like it was coming "any day now" so I was going to wait it out and report it afterwards, but if it's supposed to be the last update...
 
Anyone thinking they are waiting for the 10.9 preview to come out before releasing this?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.