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
The graphics driver version hasn't changed, so if it's in the driver, unless AMD and Apple work together on this, we may just now be stuck with this forever?
Unbelievable that the top of the line, most expensive, MacBook Pro could be left so severely crippled. The entire point of these models is the GPU acceleration, but it's destroyed and performs like a 7 year old computer any time you let the thing go to sleep.
Also particularly ridiculous that they'd get Adobe up on stage when touting the MacBook Pro, then allow all of the Adobe apps - the exact target use case for this kind of laptop - to be impacted so badly by this and other GPU-related issues. In Illustrator, currently Adobe's only solution is to disable GPU acceleration entirely, even for MacBook Pros without discrete GPUs where they say "We are aware of GPU issues on few Intel graphics card. We are working with Apple and trying to get this resolved. The fix will be in graphics driver that macOS bundles." - good luck with that.
To add extra insult to the situation, this weekend I have to go to an Apple Store 3.5 hours away, for the second time, to get my keyboard fixed... because the B key keeps randomly repeating.
Unbelievable that the top of the line, most expensive, MacBook Pro could be left so severely crippled. The entire point of these models is the GPU acceleration, but it's destroyed and performs like a 7 year old computer any time you let the thing go to sleep.
Also particularly ridiculous that they'd get Adobe up on stage when touting the MacBook Pro, then allow all of the Adobe apps - the exact target use case for this kind of laptop - to be impacted so badly by this and other GPU-related issues. In Illustrator, currently Adobe's only solution is to disable GPU acceleration entirely, even for MacBook Pros without discrete GPUs where they say "We are aware of GPU issues on few Intel graphics card. We are working with Apple and trying to get this resolved. The fix will be in graphics driver that macOS bundles." - good luck with that.
To add extra insult to the situation, this weekend I have to go to an Apple Store 3.5 hours away, for the second time, to get my keyboard fixed... because the B key keeps randomly repeating.
I’d like to chime in on this in agreement. About a month ago I bought a nearly maxed out 2017 15 inch and find it ludicrous that I have to leave my screen open 24/7 just to keep the dGPU active. A $3,000 laptop which can’t do something as simple as closing the lid without it breaking something. OMG! At this point I no longer have faith Apple will fix it, at least not in a timely fashion. May just eBay it...
I'm getting very frustrated with it as well and I'm losing faith quickly. A big part of the reason I bought a MacBook Pro instead of a Windows laptop was because I was sick of these kinds of issues. One of the big things that Apple regularly touts is that they design the hardware and the software and can therefore make sure they work together seamlessly. Yet, here we are, with GPUs in their highest end laptops that don't work properly on macOS High Sierra. Trying to get any work done means having to regularly restart and it's becoming very tiresome.
Yesterday Apple replaced the top half of my MacBook Pro to fix the keyboard, so at least now I have the newer version of the keyboard and it'll hopefully work (for a while...), but I'm very disappointed that I paid so much for a laptop that's causing me so many issues on a daily basis.
I wonder if there's any way we can draw more attention to this dGPU issue? I've seen a lot of complaints from MBP owners on Twitter aimed at Adobe and various game companies, complaining that the applications or games now run terribly on macOS High Sierra, without realising that the cause of the problem is this issue. Maybe one of those developers can be alerted and take up the issue with Apple on behalf of us, since it seems if you're not a big developer you'll get zero response.
Yesterday Apple replaced the top half of my MacBook Pro to fix the keyboard, so at least now I have the newer version of the keyboard and it'll hopefully work (for a while...), but I'm very disappointed that I paid so much for a laptop that's causing me so many issues on a daily basis.
I wonder if there's any way we can draw more attention to this dGPU issue? I've seen a lot of complaints from MBP owners on Twitter aimed at Adobe and various game companies, complaining that the applications or games now run terribly on macOS High Sierra, without realising that the cause of the problem is this issue. Maybe one of those developers can be alerted and take up the issue with Apple on behalf of us, since it seems if you're not a big developer you'll get zero response.
Last edited:
Yawn. Well that makes me happy about reinstalling 10.12.6. Performance is rock solid and I can actually use the computer as it was intended to. I don't miss a single feature from High Sierra.
Last edited:
See post #73 in this thread (link below).
https://forums.macrumors.com/thread...-from-long-sleep.2076334/page-3#post-25566055
Once again I won't be surprised if 10.13.3 releases and it still isn't fixed..just like 10.13.2, 10.13.1...
Did some testing. Found that disabling graphics switching is one workaround. A better one, however, is an App called NoSleep. It’s available on Macupdate. It disables sleep when closing the lid. Works for me until if/when Apple ever fixes this nasty bug
Update: Still happening with my 2016 MBP with Radeon Pro 460, 10.13.3 beta 1 (17D20a). Groan. SERIOUSLY.
Last edited:
Once it becomes available as a public beta instead only developer beta, I'll give it whirl and report back. Don't get your hopes up though...
Still not fixed on my 2015 with 10.13.3 beta 2. Kind of reminds me of the throttling that is apparently being done on iPhones with older batteries, but doesn't explain the issue on brand new 2017's.
I have the same macbook pro with the same issue. I took it to Apple and they replaced the entire display. I just got it back last week and haven't had the issue since. Might want to book an appointment with the Genius Bar.
I hope you all have submitted bug reports to Apple, everyone is talking about it not being fixed, but for all we know they don't even know (which is ****** in and of itself), but I really think you guys should be submitting reports to help get their attention.
What version and build of macOS are you currently running?
I've had a radar open about this issue since September and it hasn't received any response from Apple to date, despite testing each new beta release and adding an update. If anyone else is going to submit a bug report on the public beta, or a developer radar on the developer beta, you can reference mine by mentioning rdar://34677832/ in your report.
I suspect Apple knows about it but it's a driver bug and they're now at the mercy of AMD, but they should be pushing this with AMD as a top priority because of the enormous impact it has. It makes a mockery of Apple's statements about their hardware and software being engineered to work together. But given I see Adobe can't even get any action out of Apple for their GPU issues with Illustrator, I'm not hopeful. It's a disgusting situation to be in after spending so much on a machine that was supposed to take advantage of GPU acceleration for the OS and apps.
I don't think it's a hardware issue. It also happens on my 2017 MBP with a Radeon Pro 560.
I downgraded to Sierra (10.12.6) and have not experienced this issue ever since, so far so good for 12 days uptime now.
I installed it this morning, but it's a bit too soon to tell. I'll let you know what happens.
Why am I imagining this GPU issue being resolved at the same time the intel patch kills performance, resulting in a net zero gain?