-
Notifications
You must be signed in to change notification settings - Fork 30k
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
macOS Sierra: background artifacts #12473
Comments
@maxence-charriere can you try if this reproduces with our insider build too? |
Thanks for linking the related issues here. The related chrome bug is: https://bugs.chromium.org/p/chromium/issues/detail?id=633805 |
@maxence-charriere @jaysylvester that issue talks about a possible fix using |
@bpasero Just tried |
@jaysylvester great to hear that 👍 |
how to use it? I tried code --force-gpu-rasterization on the console but nothing changed. |
yeah, from the command line when launching an instance. |
|
Since 1.6.0, I'm seeing some artifacts even with |
@FabianLauer Thanks, that did the trick for me! |
Todays VS Code insider build comes with Electron 1.6.x, would be interesting to hear if this update solves this issue for anyone: http://code.visualstudio.com/Download#insiders |
Thanks for the heads up! Insider build fixed it for me without any workarounds. 👍 (Using a calibrated i1 color profile) |
It does. The colors are substantially different than before. Side by side with the same theme, the insider version colors are way more saturated. |
Awesome 👍 |
didn't work. Had to set"window.zoomLevel": 0.001 and I still see screen flickers. |
@am6377 are you on our insiders build? |
I was on insider build and then I switched to normal build to see if there
was any difference and for me there isn't.
…On Monday, April 17, 2017, Benjamin Pasero ***@***.***> wrote:
@am6377 <https://github.com/am6377> are you on our insiders build?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12473 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKWiGfQBdnWqhCv_Jj-64gYoYNTTiNqdks5rw4pagaJpZM4KEMxM>
.
|
So it looks like the Electron update is only resolving it for some people. |
@bpasero The Insiders update fixed the issue for me. No need for the zoomLevel hack now. |
@bpasero I tried #insider build but I can't use custom or other built-in display profile except for the standard color LCD which actually doesn't look really nice IRL. The only way it works for me is setting "window.zoomLevel": 0.001 and even with that I get lots of random screen flickers. |
With the current insiders build, using that specific profile (ITU-R BT.709-6), and the default dark theme, I'm not seeing the behavior, either on the built in display (5k iMac) or external display. With the current non-insiders build, I initially thought the window.zoomLevel hack worked, but after using it for awhile, it was clear that it helped some, but didn't eliminate the issue. |
The issue is resolved for me, I just verified that. No clue why some people are still seeing it though when trying our insiders build. |
It fixed all 3 machines I use which have custom profiles. Purely a guess, but maybe some people are downloading the normal version from the link posted (https://code.visualstudio.com/Download#insiders), not realizing the Insiders build is a text link at the bottom. |
Yeah, sounds like it. |
I would like to apologize to @bpasero and I would like to thank @Codelica because I realized I didn't download the insiders build. I thought the link with #insiders took to me to the insiders built. I didn't scroll down. The direct link to insiders is |
Came across this issue when scratching my head that the background colour I was setting in my theme was showing differently on the screen (i.e. when checking it with the Digital Color Meter). I did download the Insiders build and I can confirm it's fixed there for me. Can I ask when this fix will roll out? Theming is feeling rather futile while my colours don't match :-( |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: