Q: MacBook Pro (Retina, Mid 2012) freeze with Yosemite

I installed the new beta and have been running it for the past 2 days. So far, no gpu hangs and restart failures and it passes the Automatic Graphics Switching check box test.

However, now I am getting sleep-wake failures when I put the system to sleep while switching to integrated graphics. In my situation, I run a display in clamshell mode and when I leave, I put the computer to sleep by unplugging the display cable. I can repeat this around half the time even on a system with no programs open. The problem disappears if I disable graphics switching.

Silverlight does seem to make the problem worse, but I removed Silverlight and every reference to it and I still have crashes.

To clarify, my system doesn't actually crash. It hangs with everything on the screen but the mouse pointer frozen. I eventually manually reboot it and the log is full of "Trying restart GPU" messages.

I did have the absolut same phenomen  and behavior of my MBP late 2012.

It seems to be , Apple has no real interest to support und fix issues on hardware older than 2 year.

The 10.10.3 Beta has definitely fixed the issue on my mid 2012 MBPr, and I've also noticed many definite speed improvements!

Oh - good to hear.

Than I will wait until 10.10.3 is general available.

.... another user of a Mac Book Pro.

Screen freezing, cursor moves about on the screen, but thats all I can do. Have to then switch it off and on again.

Yosemite version 10.10.2

Mac Book Pro (13 inch late 2011)

Processor 2.4 Ghz Intel Core i5

Memory 4gb 1333MHz DDR3

Graphics: Intel HD Graphics 3000 384MB

Come on Apple, less about Apple watches and more about resolving the Mac Book Pro problems.

If you have read the prior posts you can see that this issue will be resolved with the Yosemite 10.10.3 update but I don't see how your issue would be the same as your MBP does not have dual GPUs so it does not have Automatic Graphics Switching. Sounds to me like your MBP may be a candidate for the Logic Board Replacement Program, have you checked into that?

I don't think that this is fixed by 10.10.3, since I just installed the beta yesterday, re-enabled Graphics Switching, and got a crash today. It's the first one that I've had since I disabled automatic graphics switching about a month ago.  My laptop probably needs the logic board replaced, and this is a hardware issue.

+1 I also thinks there is 2 symptoms encountered by users :

• some where the graphics only will reboot or crash the machine (this one CAN be software or not)
• some where the crash can make the notebook unbootable for a while and where the symptoms are the same across osx versions

In my case the motherboard replacement solved the problem and it runs now on the same osx install as before the motherboard replacement. I'm still on 10.10.2 and have no crash anymore on the mid-2012 retina (more graphic switching, sleep/wake during more days).

There are definitely multiple issues, but the issue of THIS thread has been very well demonstrated and documented here, is obviously a software issue and has been solved for many of us by the 10.10.3 beta.

I was finally able to install the beta last week after 2 dozen failed attempts, each of which was caused by a crash report for something called a LaterAgent. To achieve a successful install I had to go back to the original Yosemite 10.10.0, I then reinstalled both the 10.10.1 and 10.10.2 updates and was finally able to install the 10.10.3 beta. After the install was complete I applied the Automatic Graphics Switching test, that has been shown here in this thread, toggling the switch 30-40 times without problem. My best test, however, was within the use of Photoshop because that is where I began having this problem. With auto switching turned on, I opened Photoshop, which normally freezes immediately, without issue, I then went to the Photoshop preferences for Performance to make sure that all performance options were turned on. I then opened a 516 MB file with measurements of 39"x38" @ 300dpi and ran 3 filters. First I ran the Sharpen > Unsharp Mask filter, it ran across this large photo in 5 seconds, without issue. I then ran the Noise > Despeckle filter which made it's changes instantaneously, still no freeze. Lastly I ran the Pixelate > Crystallize filter that ran through this 516 MBs in 4 seconds, again, no issues whatsoever.

I have now been running the 10.10.3 beta for over a week and have not had a single freeze or any other issue during this entire period. The beta fixed my issues and obviously I'm not in need of a new logic board!

The same (software?) problem is still present in the latest 10.10.3 beta, even thought its occurrence has decreased greatly. I could freeze two 2013 15" rMBP I could install the beta on. I have to admit that it took about 1800 fast clicks on the automatic graphics switching in average though (clicking for about 15 minutes on these). You guys assuming all is fixed after 40 successful clicks are just not clicking enough.   If Apple could decrease the probability of this crash - let's hope they'll fix it once for all soon.

For me it's fixed. I tried switching several times not less then 200 times (before 10-20 was enough). Also i've installed it 3 weeks ago and i didn't have a single freeze, but i use photoshop every day and MBP switch the cards all the time.

May be there is a possibility to freeze MPB the same way, but a lot of work was made by Apple and this is cool.

HAHAHAHAHA.... How ridiculous! I wouldn't call clicking that switch really fast 1800 times anywhere close to average, normal or even proper usage of your computer! Try using your computer normally for a couple of weeks, then complain that it's not working properly! Any action that you desire can be forced if you try long enough!

Exactly - clicking that fast ain't a regular usage pattern as the Geniuses said. I was just trying to see if the problem is still there - because couple hours after the beta 10.10.3 upgrade I had the good old freeze just starting iPhoto. Yup, a freeze every 2 months is better than a freeze every week, but none would be much better.