Cope. Did you save your money to buy one of these expensive laptops? Do you even own one? Why must you defend Apple when a lot of us are having issues after having paid so much for a product. Jesus.
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.
16" MBP - Graphical Distortion
- Thread starter ascender
- Start date
- Sort by reaction score
Its a brilliant laptop - incredibly powerful with an amazing screen and the design has grown on me, I think it looks much better in the flesh than in the press coverage.
Yeah. I can't wait to try 4k HDR movies on there though. Gonna be awesome I think!!
That's very strange. Spookily enough, the one time I saw something like this was on a launch-day 15" MBP back in 2016 - that one did fail the hardware diagnostics but the problem was much more pronounced.
I'm not 100% on if it was GPU-related or not, but with me being away this week I couldn't take the risk and Apple really wanted the machine back to see it for some reason.
Yes, we did a clean install and upgraded to 12.0.1
Hi there. Made this account just to post. I'm experiencing this intermittently on my 14" M1 Pro. 10CPU/16GPU/16GB. It's really the exact same artifacting in the same portion of the screen under the exact same circumstance -- only when switching between desktops. I can actually keep my fingers on the trackpad when switching desktops and drag the artifact back and forth along with the desktops themselves.
I notice it's always directly below the menu bar and never encroaches on the menu bar itself. It's always below the menu icons on the righthand side of the menu bar. Given some time, it will expand downward, but so far I haven't seen it expand in width.
Logging out and back in fixes the problem. Today if it happens again, I'm going to try switching users without logging out. This is a really peculiar issue, and I'm not convinced it's a hardware problem, but I'm also not convinced it's not.
I'm not quite ready to take my brand new MacBook in for replacement, because that seems like a hassle! (I'm lazy.)
Edit: I forgot to mention that I'm also on 12.0.1.
I notice it's always directly below the menu bar and never encroaches on the menu bar itself. It's always below the menu icons on the righthand side of the menu bar. Given some time, it will expand downward, but so far I haven't seen it expand in width.
Logging out and back in fixes the problem. Today if it happens again, I'm going to try switching users without logging out. This is a really peculiar issue, and I'm not convinced it's a hardware problem, but I'm also not convinced it's not.
I'm not quite ready to take my brand new MacBook in for replacement, because that seems like a hassle! (I'm lazy.)
Edit: I forgot to mention that I'm also on 12.0.1.
Last edited:
Hi guys! The issue came back, and I've taken some notes about it this time. Here are my observations.
- Artifact scales with display scaling.
- Does not resolve by disabling ProMotion.
- Began at the start of a Microsoft Teams video call.
- 11.31GB memory used. 10-20% GPU. ~10% CPU.
- Switching to a different user resolves the issue with no decrease in memory usage. Switching back to the affected user brings the issue back.
- Ending the Teams call did not resolve the issue.
- Quitting Microsoft Teams immediately resolved the issue.
Ascender, do you use MS Teams? I'm not convinced Teams or Chromium is the real cause of the issue, but it is an interesting observation.
- Artifact scales with display scaling.
- Does not resolve by disabling ProMotion.
- Began at the start of a Microsoft Teams video call.
- 11.31GB memory used. 10-20% GPU. ~10% CPU.
- Switching to a different user resolves the issue with no decrease in memory usage. Switching back to the affected user brings the issue back.
- Ending the Teams call did not resolve the issue.
- Quitting Microsoft Teams immediately resolved the issue.
Ascender, do you use MS Teams? I'm not convinced Teams or Chromium is the real cause of the issue, but it is an interesting observation.
Yes, unfortunately I have to use Teams every day!
I've got a 16" M1 Pro now and the issue hasn't occurred on this one.
Like you, logging out or rebooting seemed to make it go away but it would quickly come back. I didn't try it with a different use account though as Apple were keen to get the laptop back.
Thanks for your reply! Interesting. I'll keep an eye on mine and see if it only happens when Teams is running, or if I can get it to happen without. I have two accounts on my Mac. One is for work and usually has Teams running, and the other is for home and never does. So far, I've never seen the artifact on my home account.
I did notice that the second time the artifact appeared today, a background process that I assume was from VS Code called "Code Helper" was the top GPU load at about 6%.
A moment of silence for everyone on this Earth who has to use Teams on a daily basis. You have my empathy.
I did notice that the second time the artifact appeared today, a background process that I assume was from VS Code called "Code Helper" was the top GPU load at about 6%.
A moment of silence for everyone on this Earth who has to use Teams on a daily basis. You have my empathy.
I never realised they made one that size.
That really can’t be classed as a portable machine.
Interesting. I've been using Microsoft Teams on my 16" M1 Pro without any problems. Daily uses of video calls etc and no problems. Vscode also doesn't cause any problems.
Though, I am using 12.1 beta 1 . So it might be a stable bug?
White7561, that is interesting! I'd love it if they fixed whatever this is in 12.1. That said, I'm sure that if absolutely everyone in the world using MS Teams experienced this bug, there would be a lot more Google results for it than just this thread.
I still haven't been able to make the artifact happen without Teams running though, even when playing four 4k videos in Firefox simultaneously to push CPU, GPU, and memory load to similar levels as a Teams conference call. I'm still suspicious that VS Code might be able to do it though -- maybe an Electron thing? -- and I'm going to be using that a lot today, so I'll keep paying attention.
I still haven't been able to make the artifact happen without Teams running though, even when playing four 4k videos in Firefox simultaneously to push CPU, GPU, and memory load to similar levels as a Teams conference call. I'm still suspicious that VS Code might be able to do it though -- maybe an Electron thing? -- and I'm going to be using that a lot today, so I'll keep paying attention.
Interesting! I'm not happy to hear that your new M1 Pro has started displaying the artifact, but I am happy to see some more suggestion that it's not a hardware problem -- or at least not a hardware fault.
For what it's worth, I still haven't been able to make this glitch appear without Teams running, even under heavy workloads. With Teams running, it's 100% certain to happen within an hour or so, sometimes less. I kinda wonder if it has something to do with Teams' custom notifications. They appear around the same area where I see the glitch.
For what it's worth, I still haven't been able to make this glitch appear without Teams running, even under heavy workloads. With Teams running, it's 100% certain to happen within an hour or so, sometimes less. I kinda wonder if it has something to do with Teams' custom notifications. They appear around the same area where I see the glitch.
Interesting. I use the native Mac notifications and don't have this problem. It could be that
It seems like most, if not all the problems are with the 16" MacBooks, my 14" is superb in every way possible.
About a year on, faced exactly the same issue on my MBP M1 Max 64GB.
The culprit is in-fact MS Teams and the issue hasn't been resolved as of this comment. This happens when the notification-style is set as "Teams built-in". You can head over to the MS Teams settings > Notifications and change the style to native Mac banners to circumvent this.
It's sad to see Teams let such bugs remain unsquashed for over a year.
Honestly made me scared that my machine was already showing artifacts.
The culprit is in-fact MS Teams and the issue hasn't been resolved as of this comment. This happens when the notification-style is set as "Teams built-in". You can head over to the MS Teams settings > Notifications and change the style to native Mac banners to circumvent this.
It's sad to see Teams let such bugs remain unsquashed for over a year.
Honestly made me scared that my machine was already showing artifacts.