-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Provide way to check chrome://gpu #92586
Comments
|
@seawalk24 can you please expand on what basis you think the argv.json flag is not working. Thanks! @hangtwenty the issue you are facing is different, its #92420. Please follow that issue for updates. |
@deepak1556 I am running VS Code in a virtual machine that has major graphical issues if I don’t run it with the —disable-gpu option. I’d like to not have to specify the —disable-gpu option every time and instead use disable-hardware-acceleration in argv.json but when I do this the graphical issues are present. |
Hey @deepak1556, this issue might need further attention. @seawalk24, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
Sorry for the delay, thanks for adding more context. Can you provide some steps to repro this issue, what vm and OS to use etc |
The graphical glitching is occurring on MacOS 10.15.5 using Parallels 15. The purpose of this bug report is not to fix the graphic glitching because similar glitching occurs elsewhere such as opening a Finder window with 2 tabs. The purpose of this bug report is to make it so that disable-hardware-acceleration is utilized when specified in argv.json so that it won't be necessary to specify --disable-gpu every time as a command line parameter. I suspect that disable-hardware-acceleration may not be working even outside of a VM. |
Unable to repro with latest stable. |
I am experiencing this with the latest version of VSCode. Adding I believe I am experiencing the same graphical glitches that the OP was experiencing. In any case, I'm trying to disable hardware acceleration in order to workaround these glitches. Like the OP said, I do believe that the glitches are not a problem with VSCode but rather with MacOS. See this thread for more information of the problem which occurs in other applications as well (perhaps all of them are Chrome-based?): https://forums.macrumors.com/threads/strange-chrome-browser-graphical-glitches.2229803/ VS Code version: Code 1.51.1 (e5a624b, 2020-11-11T01:11:34.018Z) System Info
Extensions (10)
|
@deepak1556 Could you reopen the issue please? |
@deepak1556 This is still an issue, please reopen. |
I'm unsure if it's completely relevant to this issue, but I noticed VS Code (or is it Electron?) attempts to use GPU even when vscode-still-using-gpu.mp4 |
Thank you for sharing the video. What you are describing is exactly what the issue is here. CC: @deepak1556 |
@ChadMcCaffery the gpu process will be launched even when hardware acceleration is disabled, the name is bit misleading but this process is also responsible for software rasterization. The right way to check if hardware acceleration is used should be via loading Side note: @ChadMcCaffery the gpu process failing to launch in your case is a side effect of trying to open the application as an administrator. Due to the nature of sandbox profiles applied to the different processes in the application, you should launch the application as non-elevated to have a stable experience. |
Thank you for the explanation. I learned something today! 😄 |
Launching VS Code with --disable-gpu works but adding disable-hardware-acceleration to argv.json has no effect.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: