New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode flickering on mac (macbook air M1 ) while using with external display. #165681
Comments
I have the same problem with my MBA M1. |
The same on mbp 14 m1pro |
I am experiencing the same issues. Very problematic as it is occurring more frequently as of today for me. But the problem started when updating to MacOS 13.0 |
Same issues. MacBook Pro 16 and external Benq 4k display |
same issue |
M1 Max MacBook Pro 16 and external Benq 4k display. |
Yeah, same exact issue. M1 chip MacBook Pro 14 inch. |
Me too. Following. |
Me too, MBAM2 external Samsung monitor. |
Please try our exploration build based on newer runtime and confirm if the issue still persists. Thanks! |
Mine flickers very fast, in both the stable build and the exploration build. Gets worse or better depending on the window position. Able to reproduce when
I wasn't able to reproduce when VS Code was set to LaptopMacBook Pro External DisplayBenQ PD3220U, 4k 60hz, used as main display, macbook in clamshell mode |
Having the same issue lately |
The flicker is bad, gives me a headache. The external display on the macs hdmi port is the culprit. The laptop screen and the other connected with thunderbolt never flicker. External Display: Asus VS247. |
Having had my m1 mac for a long time, using my m1 mac mini as a headless server and for work I already switched to "normal" x86 machine. Problem is even worse when running asahilinux. But, hear me out: It is rumored that its a issue with EDID, which could mean that running your display with a capture card that has passthrough in between could actually help. Cost around 160 bucks ( e.g NZXT Signal 4K30 ) Alternatively could try a EDID Emulator device. But it could also be a regional issue - some machines may not have the issue, produced somewhere else.
@kferrone thats absolutely correct. Those were also the findings in the link posted above... |
Happened to me on my M1 macbook pro after I switched from HDMI to USB-C/Displayport. After I switched away from "Solarized Dark" theme to "Dark+ V2 (Experimental)" the flickering went away. |
I doubt it has to do with the theme. Can you let me know if you don't have any flickering for the next couple days? |
I have now switched back to HDMI from the MacBook. Now the flickering is gone. Seems like it doesn't have anything with VS Code Theme. It seems to be a USB-C problem with a BenQ 4K monitor. |
@aneelang After looking at the video I think my issue is different. My flickering is much quicker than the reporter's. It almost looks like it's doing interlacing like an old TV, except it's vertical and not horizontal. Also it makes the whole monitor flicker even if code is only using half of the screen. It does not stop flickering until I change the theme or I remove "black" dialogs hovering over the main editor window. I agree that it's not likely the theme but maybe it could be the rendering/contrast? I could get it to happen pretty consistently by doing the following:
Having the almost-black background of the dialog hover over the slightly lighter background of Solarized Dark seems to be the trigger. I tried a few other themes but couldn't re-create it as noticeably. After I restarted Code today I could not reproduce the issue. I've had it open for several days including suspend/resumes. Other notes
|
@jagibson I absolutely have no evidence about what I'm about to say: |
I am having the same issue. The flickering on my screen is very rapid. Just bought a brand new MacBook Pro M1 Max 32 GB RAM and my screen flickers when I use full screen visual studio code with HDMI to an external LG monitor. Will continue following. |
Update 4/4/2023. I replaced my Macbook. The technician said it was not vscode or any other software. It was the hardware related to the display. |
This absolutely is an issue with VS Code. No other app triggers this, and its happening to a lot of people. M1 Mac, Dark theme (Solarized dark), external display (1440p 165Hz) over HDMI |
I found a workaround ... mostly. I make sure every workspace only has one single theme extension enabled. I went to all my workspaces and disabled all themes globally first. Then in each workspace, I only enable the extension for the theme I want in that workspace. This means all the others theme extensions are disabled. If I enable every theme extension in a workspace and then choose a theme, the flicker will get bad. I am also suspicious of too many extensions in general so I only enable extensions selectively per workspace and have all global extensions disabled. I blame extensions fighting with each-other. |
I have a M1 Mac too and other apps trigger this as well It is not really undermining the point I had made, rather a secondary possible cause. In some electron based apps like microsoft teams, it can help to deactivate the hardware acceleration. Sometimes it is so bad it can trigger epileptic seizures... and thats not even on a M1 device, it's on a x86 lenovo thinkpad laptop. But it is completely possible that a large quantity of electronics are faulty and won't be replaced with a working model / can't be fixed. It could also be possible that this issue is related to which batch you got and in which region you bought your device. Of course: Those are the less common "individual cases"... right? By the way: I had screen related issues even when on Linux, booting from a M1 device. And they were even much more likely to show up. I suggest to get either a new apple device or start using a 'normal' x86 device. FYI Theres also this https://www.eizoglobal.com/support/compatibility/pc/mac/apple-m1/ which is a statement regarding limitations about m1/m2 devices. But not so much related to flicker. |
happens with me too. |
This was happening to me when using a MacBook Pro (Apple M1 Pro, Ventura 13.4) and using a Samsung G9 Odyssey monitor in Pip mode (split screen). It would cause my other split to flash and be very distracting. It would only happen when the terminal window was visible on the Mac. You could resize the window to zero height or close it entirely and it would stop happening. To solve this, I changed my theme from |
I think @zDEFz is right - the issue is deeper than vscode. I had it happen with Microsoft Remote Desktop (another MS product?) when connecting to a remote server that had just the right subdued colors. |
Not a recommendation, just an observation. I've checked on the thread I've posted before once again. There is a person claiming to have found a fix with 'technically an external GPU' I haven't tried it personally. It involves buying a 140 EUR adapter OWCCADPDL2HDMI https://www.amazon.de/OWC-Display-DISPLAYLINK-Thunderbolt-OWCCADPDL2HDMI/dp/B09RMVL865 and a 10 EUR HDMI Emulator. ---snip---
Cons:
|
The flicker is even worse when you are already feeling nauseous. Uggh, this about made me puke today. Just wait till someone has epilepsy and comes across this one. |
Not all triggers are visual. Any type of stress can trigger epilepsy as well. |
Potential fix: Switch color profile to "Generic RGB Profile", it worked for my m2 laptop + external monitor [reddit] |
For me switching the theme Dark+ worked as a temp fix for the flickering on my BenQ 4K external monitor. |
Disabling the "True Tone" option in system preferences seemingly fixed the flickering for me. Laptop: MBP 14in M2 Max |
I was getting the flickering pretty bad with an older (2018, non-Apple Silicon) MBP Model: MBP 15in 2.6 GHz 6-Core Intel Core i7 UPDATE
https://stackoverflow.com/questions/29966747/how-can-i-disable-gpu-rendering-in-visual-studio-code |
These two combined steps worked for me:
|
I recently ran into this with a Samsung LF32TU87 monitor. While setting the Color profile did not resolve the problem, using the native resolution did. Thank you spockoyno! |
The one thing that worked for me was disabling GPU rendering. Preferences: Configure Runtime Arguments, add |
This worked for me, though scrolling seems not so smooth now. But it's much better than that flickering. |
This resolved it for me...
|
Apparently, |
To sum it up - Apple did mess something up, and it is working if it doesn't use Apples implementation? |
For me, changing the resolution ratio worked on my Dell. It didn't like the intermediary options. I had to scale it all the way until it matched a native resolution of the monitor. This makes sense to me. Apple seems to be generating resolutions based on UX, rather than hardware capability. |
You know, its all kind of weird. On my older macbook pro from 2016, after update to ventura/sonoma, Microsoft Teams is only usable through the Browser if NO external display is connected. Otherwise, the whole application becomes non-interactable. |
In my case the flickering stated after the sonora update (M1 max pro laptop on a 4k asus monitor), and stopped when i disabled the hardware acceleration from |
So, is there no solution to this except for disabling the hardware acceleration, which by itself comes at a cost of reduced performance? |
These are all guesses. What works for you might not for others. On top, you have issues if you do not use apple displays. Why? Well, because apple does do their own stuff. See https://social.treehouse.systems/@marcan/112129842235465322 |
MacBook Pro M1, Dell external monitor. I tried various other things mentioned on this thread, but in the end, switching from scaled -> default resolution on the monitor worked. Flickering was pretty bad, triggered by scrolling and typing. |
Intel Macbook Ventura 13.6.6 -> Turning off "Zoom per window" fixed it for me. Having multiple windows/split windows makes it worse. |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Flickering happens on the main and external display as well. Flickering is random. Sometimes the screen goes black for a long (3-4 secs). Sometimes it flickers continuously.
Will publish more related videos. It's pretty random. Unable to record all situations.
VID_20221107_110756.mp4
The text was updated successfully, but these errors were encountered: