ifeltsweet wrote:
Experiended second freeze with a macbook air 13' mid-2012, no haswell then, occured using safari in full screen
definitely software heh ?
At this point we can say: defently not a hardware error by itself.
The most likely is that (out in easy words) some chipset might have something like a boundary.
Let's say, for a simple example, the USB chipset needs 5 milliseconds to send an "answer" if "asked" from the operating system, whether it is sleeping or not.
In the past, OS X asked this question to the chipset and waited 10 milliseconds.
Due to variation at the assembly process, some chipsets needed 6 milliseconds to answer. It is not that they are "broken". They are simply a little out of predefined boundaries.
Still all good, since they are inside the boundary of OS X.
Then Mavericks comes along. Due to max out the power savings, Mavericks has been programmed to wait 5 milliseconds, no longer.
What happens now is, that a few older devices start to have the freeze problem. Because their chipset (which should take 5 milliseconds to respond) need 6 milliseconds to respond.
And the 13" rMBP has a chipset on the board which always takes 7 milliseconds. By design? We do not know and probably never will.
All this as a very simplyfied example, so non-technical people get an idea what I am talking about.
So we are very very unlikely talking about broken hardware here. I see no way, it is "broken". Way too many devices are affected for that. Most likely, something is just a little out of boundaries. You can look at it from two perspectives: the boundary of the operating system Mavericks is too tight. Or the boundary of the hardware is too loose. Both perspectives are right in a way. Since older devices areaffected, too, it seems Apple tryed a little too hard to max out the power savings. I assume, on the build 13A2093 of Mavericks for the 13" rMBP they maxed it out even more, because they really, really wanted those 9 hours of battery life for this device.
Of course, now Apple is in a dilemma. They said "Our ner Mavericks is fantastic, it gives you extra battery life". Now they might have found out, that it simply doesn't work on too many devices to accept it. Now what? Fix it in Mavericks, but then go out and say "sorry, now Mavericks does not anymore give you that much extra battery life"? Wouldn't sound good.
I think, the software engineers are now working very hard. Not on fixing the bug. I assume this was a matter of only a few hours. But now they have to search elsewhere for an option to save some extra % of battery life.
Return the hardware because of all of this? I wouldn't. Nothing seems to be broken (and if, Apple would exchange it even after months, not just after 14 days).
These are my personal thoughts and ideas about this topic. Please note that they are not based on any official information from Apple. In the end, you have to decide yourself, whether you want to wait, or whether you want to return your device.