Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2017 MBP 15 - Radeon GPU does not work after resume from long sleep
- Thread starter jeh72
- Start date
- Sort by reaction score
I had it happen once with beta 4 right after install, but not after a subsequent restart. I chalked it up to being in a funny state right after install. With beta 5 I seem to trigger it more easily.
I don't know. I've seen it happen with both the integrated Intel and discrete AMD GPU's on all releases of High Sierra. The issue with AMD being the most noticeable since it kicks in when you are pushing the GPU. But now the AMD issue seems fixed with beta 4 & 5. Just need to get the Intel GPU's behaving now.
Really concerned with what I see as sloppiness with High Sierra. Both developers and QA.
I don't know. I've seen it happen with both the integrated Intel and discrete AMD GPU's on all releases of High Sierra. The issue with AMD being the most noticeable since it kicks in when you are pushing the GPU. But now the AMD issue seems fixed with beta 4 & 5. Just need to get the Intel GPU's behaving now.
Really concerned with what I see as sloppiness with High Sierra. Both developers and QA.
Could be a 2015 MBP 15" model problem only. All along with High Sierra I've seen the problem with both the iGPU and dGPU, the dGPU hopefully now being fixed with the latest betas. At least for the 2015, I don't think the iGPU problem is new in the latest betas.
I have something called iStat Menus. Well worth the money. Sits on the menu bar at the top. If you select to see the CPU, it shows you which GPU is active, how much memory is used currently, last hour, 24 hours, week and month. Same thing with the processor. With multiple desktops, I'll switch between X-Plane and an empty desktop to view what's going on with the GPU. Cool stuff.
http://gfx.io
gfxcardstatus shows which graphics are in use and allows you to lock the machine to either iGPU or dGPU if you want. I use this to lock to iGPU when I want to max out battery life.
gfxcardstatus shows which graphics are in use and allows you to lock the machine to either iGPU or dGPU if you want. I use this to lock to iGPU when I want to max out battery life.
Also, to see which gnu is being used:
Determine which graphics processor is in use on your MacBook Pro
Find out if your MacBook Pro is using a discrete graphics processor (GPU) or an integrated GPU.
MacBook Pro 15-inch and 17-inch notebooks often have two graphics processors (GPU)—a discrete GPU and an integrated GPU. The discrete GPU provides substantial graphics performance but uses more energy. The integrated GPU optimizes battery life by using less energy.
Determine if the discrete or integrated GPU is in use
Determine which graphics processor is in use on your MacBook Pro
Find out if your MacBook Pro is using a discrete graphics processor (GPU) or an integrated GPU.
MacBook Pro 15-inch and 17-inch notebooks often have two graphics processors (GPU)—a discrete GPU and an integrated GPU. The discrete GPU provides substantial graphics performance but uses more energy. The integrated GPU optimizes battery life by using less energy.
Determine if the discrete or integrated GPU is in use
- To see which graphics card is in use, open About this Mac and go to the Displays Tab.
Nah, it still has a beta release number, unlike the lates iOS beta this week which received a GM candidate build number.
Just had my Integrated Intel Iris Pro go into slow motion mode after it slept for an hour today. But it had been ok since I installed 10.13.3 on release day and was hoping it was fixed. Haven't seen it happen on the AMD GPU for the last couple betas and release of 10.13.3. Mines the 2015 MBP 15".
I don't think I've experienced the Intel issue on my 2016 MBP, but I'll keep an eye out.
The Radeon issue appears to still be fixed in 10.13.3 final for me, so I've now marked my radar as closed. Interestingly, once I marked it as closed I can now see that my radar is a dupe of another radar that's still open, so make of that what you will.
The Radeon issue appears to still be fixed in 10.13.3 final for me, so I've now marked my radar as closed. Interestingly, once I marked it as closed I can now see that my radar is a dupe of another radar that's still open, so make of that what you will.
WoW changed how it handles window/full screen mode. It results in pixel doubling/quadrupling