Display Issue - Horizontal blue lines in application windows

As you can see from the image below I have blue horizontal lines appearing within my Chrome application window


2019 Macbook Pro 16


The application is the latest build of Chrome Version 80.0.3987.163 (Official Build) (64-bit)


It has happened 3 times now - each time appear to be after the laptop has been left running overnight.


Not it is not the full display affected only the application window. I've also only seen this in the chrome browser (I've also posted this to the Chrome support site) it sometimes goes away simply by killing Chrome but this time required a reboot.


Anyone seen this before - got any ideas??




MacBook Pro 16", macOS 10.15

Posted on Apr 5, 2020 7:14 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 28, 2020 6:09 PM

I was having the same issue. I found a post on Google Support which worked for me.


I went into Chrome settings and toggled off the "Use hardware acceleration when available" option. Then hit the "relaunch" button next to the hardware acceleration toggle and the problem was fixed - no blue tint anymore.

195 replies

May 9, 2020 12:21 PM in response to joshintosh

I take that back. If it fixed anything, it was temporary. It's right back to the same problems.


joshintosh wrote:

For the record, I cleared NVRAM or "PRAM" several times in a row yesterday and left my computer on overnight. For the first time in a while there was no message about the computer restarting unexpectedly or any funky lines in my apps that have hardware acceleration in the morning. Seems to be working so far.

How to reset NVRAM or PRAM on your Mac -> https://support.apple.com/en-us/HT204063


May 17, 2020 1:55 PM in response to joshintosh

Glad to hear Apple's aware of the problem. I've been having the blue screen appear once every 2-3 days while using chrome. I don't use any intensive software—only VSCode and Chrome mostly and still get the blue screen.. sometimes the issue arises while only having browser on.


I have—"Enable Power Nap", "Prevent computer from sleeping"—all turned off by default, and have always been shutting off the computer when not in use and still have the blue screen problem. But also, the computer seems to be overheating quite frequently even without using any graphics or RAM intensive programs. I can literally see the dust marks in the shape of the fan vent on the bottom bezel of the display. Hopefully this helps the Apple team work on the problem somehow..


MacBook Pro (16-inch, 2019)

Processor 2.3 GHz 8-Core Intel Core i9

Memory 16 GB 2667 MHz DDR4

Graphics AMD Radeon Pro 5500M 4GB

Intel UHD Graphics 630 1536 MB

External Display LG HDR 4K Display 27-inch


EDIT: Restarting the computer will temporarily fix the problem, but the same blue screen issue arises around—1 day to 2 days later.

Dec 8, 2020 5:57 AM in response to fexnok

For what it's worth, I have not had the issue occur for a while. I have a 3 monitor set up using a CalDigit docking station on my Macbook Pro 16in. 1 monitor is a 4k monitor, the other is a standard monitor and the 3rd is the macbook display. I am not positive if the events are related but when I am done for the day I have been keeping my macbook connected to the docking station and started closing my macbook to make it go to sleep. It's probably been a good month or so since I've had the blue line issue. I thought I would share. Thanks

Apr 11, 2021 2:27 PM in response to Mauricio Drelichman

FWIW, they replaced my mainboard requiring me to then rebuild my system from a backup, when I reported it to the local Genius bar, and the issue remained. That said (and I'm knocking on as much wood as I can find around me now) at some random time after that, it just stopped. I'm still using the same setup, settings, outboard adaptors and dongles, monitors, etc, and it hasn't happened in weeks. I don't know what's more frustrating, that it happened at all, or that I don't know what I did to make it go away...

Apr 14, 2021 4:03 PM in response to pbengou

Clearly, there's an issue with the GPU in the MacBook Pro 16" 2019 and software that uses the Chromium devkit that causes this to occur. Apple's acknowledged it in another forum post that I can't find now, but they said that they were talking to the Chromium team at Google about it, but something tells me that nothing is going to be done about it.


I find this a disappointing response from both Google and Apple. It might be worthy of a class action lawsuit? This might be the only way we can get compensation and recompense for the lack of action in remedying the problem...


Thoughts?

May 24, 2021 5:38 PM in response to ileradeltercomondo

Thanks for providing the update, @ileradeltercomondo.


That is the worst of my fears – that potentially, this issue is inherently a hardware architecture and implementation fault that cannot be resolved in software without massively crippling the function of the GPU. I hope this can be proven otherwise from Apple. Something perhaps to do with how Apple integrated AMD's GPU core into this particular generation of Macbook Pros? It has been a nagging hunch that I've had for a while, especially seeing how we haven't gotten any fixes or updates from Apple.


It has officially been more than a year since this was reported. I am still abhorred at how I was led to think this was Google's fault in my initial Apple tech support outreach.


Those who continue to parrot resetting NVRAM or to disable hardware acceleration, keep drinking the Kool-aid. The rest of us here are looking for a resolution to getting our machines working – the way they were spec'ed and advertised to us – and that we depend on the stability of our machines to work when we expect them to.


My display continues to glitch. The easiest way to reproduce this is to leave the MBP plugged into a second display, let it go to sleep for a few hours while you have a web browser window (or any WebGL application) running, and wake it up. That said, I have also encountered the same glitch without a second display. The trigger point is almost always waking the computer from sleep – although these days just coding a WebGL app and testing it on browser refreshes can also trigger it.


Have there been sufficient fellow users who have submitted a tech support case to Apple, quoting this discussion?


To the Moderator: what did you edit in ileradeltercomondo's post? Some transparency will be useful here given the nature of this case.

Jun 8, 2021 6:57 PM in response to TeeMarkM

Pretty certain that the problem being seen by the people in this forum thread is not a hardware fault per se, but a design flaw. An unforeseen incompatibility that now uncovered, is too hard to fix without designing a new combination of hardware and swapping out the computers with anyone that's bought one of these 2019 16" MacBook Pro models. Clearly, this would represent a PR disaster, a somewhat serious financial hit, and a lot of egg on a lot of faces.


This particular problem being discussed here has nothing to do with authorised service centre or Genius Bar staff. Nothing to do with support reps who are as blind to the real reason this is happening as the market is. Nothing to do with quality of manufacture.


A number of us who have seen this problem have had complete logic board replacements carried out by well-meaning, highly professional and ethical Genius Bar reps, only to find that the problem keeps happening.


Make no mistake. This is a minor scandal affecting a group of mostly unorganised consumers and one that a very large corporation with massive amounts of legal horsepower has already calculated the risks involved in ignoring the affected customers and decided that ignoring it is the most viable course of action.


Prove me wrong.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Display Issue - Horizontal blue lines in application windows

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.