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
Black Pull Down and Titlebar Menus #98924
Comments
Same issue with closed issue #94361 in exploration version. |
Can you check if the insiders version work fine without disabling gpu acceleration https://code.visualstudio.com/insiders/ |
Same problem (with the insiders version 1.47.0), after 10 min of utilisation (tried twice). This time the whole application froze (cannot do anything other than open the black menus and do a right click to open another black menu). I had to quit the application. |
@mathisgag are you also using virtualbox vm ? |
Yes, I am also using virtualbox vm. (Running XUbuntu20.04) |
Is it any better when you use |
Yup thats correct, in that case how does it look with custom titlebar ? Can you also confirm if you see this issue with https://github.com/electron/fiddle/releases/tag/v0.15.1 , you can try electron versions |
Switching to the custom TitleBar fixes the issue on vsCode version 1.46.1 and vsCode Insider version 1.47 . I had gpu acceleration enabled and the Title bar to custom for half a day of work on the official version and I didn't encountered the issue. Plus: The custom title bar looks cool! |
This is a duplicate of #84745 |
Installed VS Code on new install of guest of Debian 10.4 with KDE Plasma within a VirtualBox 6 VM on a Windows 10 host. When running code with the gpu enabled, pull down menus are rendered as black. Moving between menus sometimes gets them to render properly, but moving between menus again can turn them back to black. Clicking in the black, chooses a menu item as if it were visible.
Running code with the gnu-disabled flag, eliminates the problem. All other 3D accelerated applications seem to work fine, so this seems to be something particular to code.
I think this is the same issue as the closed issue:
#72302
However, hopefully, this information is enough to reproduce. The GPU in the machine is a RTX 2060.
The text was updated successfully, but these errors were encountered: