Strange Chrome browser graphical glitches

[Lp734]

Yeah, I’m experiencing the same issue on a brand new MacBook Pro 16”. Just adding to the conversation to keep the post relevant. Hoping for a permanent fix soon.

 

[traCkready]

Has there been any convergence if exact external display config matters? I am going through a Cal-Digit TS3+, I am wondering if a thunderbolt to DP/HDMI right off the Mac changes anything?

 

[thehesiod]

has anyone logged a chromium bug? I have the same issue

 

[thehesiod]

actually I just filed https://bugs.chromium.org/p/chromium/issues/detail?id=1171946 so please star/upvote

 

[systemBuilder]

I just experienced the problem yesterday.

I found an article that suggests using _partial_ GPU disabling. Perhaps we can figure out what part of the GPU code has the bug? The article is here:

[FIX] Chrome graphics issues (but without turning off graphics acceleration!)

I am not sure how many people this effects, but I imagine a number of users with a relatively recent NVIDIA or AMD GPU have been experiencing persistent graphics issues in Chrome since at least 10.11. These issues include: Garbled browser page content, often appearing as blocks of the page...

www.tonymacx86.com

- Don Gillies, Databricks, Inc.

 

[karlisrode]

Thanks to the previous post, I managed to solve my issues...! 🤗

Following ALL steps in https://www.tonymacx86.com/threads/...out-turning-off-graphics-acceleration.221328/ finally solved it for me. Thanks to https://forums.macrumors.com/thread...es.2229803/page-4?post=29554425#post-29554425.


Chrome: Version 88.0.4324.150 (Official Build) (x86_64)
OS version etc: see screenshot.

 

[eysiskal]

It's crazy that there still isn't a fix for this issue. I wonder where the root of the problem lies.

 

[apache2]

Just adding to the pile...

I got a new MBP 16" (with maxed out specs, work machine) this week and immediately ran into this issue. Amazingly frustrating this is happening on a $5000 device.

I'm on macOS Catalina 10.15.7 (19H524), and I get the affect no matter which version of Chrome I try.

 

[MacFlop]

I just experienced this too using Chrome (88.0.4324.192). Using a MBP 16" 2019 5300M with Big Sur 11.2.1 connected to two external displays.

 

[HeikoK]

I only signed up to report that this issues still persist.

MacBook Pro 16" 5300 M
Big Sur 11.2.1
Samsung 49" via CalDigit T3+
Chrome and Franz / WhatsApp
(VSCode runs fine)

 

[JackyChan]

It seems that all 16-inch MBPs have this problem. Even turn off GPU rasterization isn't take effect for this link

Web Augmented Reality

webar.istaging.com

Firefox also has the same problem.

MacBook Pro (16-inch, 2019)
Processor 2.3 GHz 8-Core Intel Core i9
Memory 32 GB 2667 MHz DDR4
Graphics AMD Radeon Pro 5500M 4 GB
Intel UHD Graphics 630 1536 MB
Chrome Version 89.0.4389.114 (Official Build) (x86_64)

 

[fakesonic]

This is still super annoying. Seems to be a lot more frequent as of late.

 

[ferdi2005]

This happened me also in Safari today.

From the Chromium.org bug:

Comment 249 by kbr@chromium.org on Tue, Apr 20, 2021, 7:31 PM GMT+2 (5 days ago)
Apple has confirmed that they have a fix in hand and that it's being considered for a forthcoming macOS software update.

 

[rickythefox]

Haven't experienced this issue for a while, then it popped up again today. The only pattern I see is that I started my Windows 10 guest OS in Parallels for the first time in a pretty long while. The glitch resolved itself after a reboot... Can this be related to Parallels somehow?

 

[itsaleeb]

Happened to me again today. So annoying. Disabling hardware acceleration for me worked but I recently updated to Big Sur and appeared again on my Whatsapp app. I hope there's a better solution soon.

 

[fhamel93]

I had exactly the same bug for months and it was worst every weeks. Always had a greenish screen when using Chrome or Electron based app after a few minutes or hours. I took it back to Apple and they completely reset the mac and reflash the T2 chip. Didn't had the bug for at least 2 weeks since ! The bug was only happening when using an external monitor as a secondary display tho.

Pretty sure the bug is linked to the T2 chip since a reset prior to bringing it back to Apple didn't fixed the bug.

 

[TheJulianJES]

Should be fixed in macOS 11.4. Didn't have it happen (yet)

 

[alexdilley]

I've been on macOS 11.4 for a couple of days now and haven't experienced the glitch — it would normally happen within a few hours. So, "hallelujah!", after many, many months, this may have fixed it (touch wood!)!

 

[errrr]

This just happened to a coworker of mine yesterday in Chrome with no external display attached (she never use those). In fact, nothing other than the charger was attached to her Mac (via wire).

She's using MBP 2019 16', Catalina 10.15.7.

 

[zantell1]

made an account to reply that I finally think the bug is fixed on 11.4

 

[TheJulianJES]

Still/again present in macOS Monterey 12.0 Beta (21A5248p).

 

[serge94]

It was kinda fixed in the latest Catalina version... only had an issue like once every 3-4 months. I just upgraded to the latest Big Sur (11.4) like one week ago and it started happening again...

 

[Jobeo]

Have been using a 2019 MBP w/RaedonPro 5500M under 10.15.7 w/two external TB displays for about 3 months now. This issue happened a few days ago in GitKraken use (an Electron app) so I closed it and didnt see it again.

I ran an Catalina update today after which the system rebooted. This issue happened again so I closed/exited GitKraken and re-opened it and the screen was the same. I went to search Goggle about it in Chrome and the the Chrome window experienced the bug. I placed the computer to sleep for a few seconds and woke it back up and both apps graphics are clear and working w/o displaying the issue... for now. Waiting for it to come back before I try disabling hardware acceleration in Chrome but not sure how this popping up in GitKraken before it happened in Chrome would have a Chrome change affect it...

WTH?!

 

[ttpjd1]

Hmmm, I had this issue in the early days (top spec MacBook Pro 16, 2.4Ghz 8-core, 2TB, 32TB, 5500M) and it's back again just now. Can't remember how I fixed it last time. So far it's visible in Google Chrome only. Been running some scientific calculations recently that caused the fans to work hard so I'm wondering if the heat has damaged something. Have been using the machine closed, with an external display connected. Guess it's time to call Apple support again. They were pretty good when my Touch Bar failed 6 months ago.

Update: As others suggested, deactivating hardware acceleration fixes the issue in Chrome. Guess I'll see if it rears it's head anywhere else...

 

[TheJulianJES]

Hmmm, I had this issue in the early days (top spec MacBook Pro 16, 2.4Ghz 8-core, 2TB, 32TB, 5500M) and it's back again just now. Can't remember how I fixed it last time. So far it's visible in Google Chrome only. Been running some scientific calculations recently that caused the fans to work hard so I'm wondering if the heat has damaged something. Have been using the machine closed, with an external display connected. Guess it's time to call Apple support again. They were pretty good when my Touch Bar failed 6 months ago.

Update: As others suggested, deactivating hardware acceleration fixes the issue in Chrome. Guess I'll see if it rears it's head anywhere else...

Which macOS version are you running? The software issue was fixed on Apple‘s side and the patch should be in macOS 12.1.