Add Render Glitch Workwaround to DOCS.MD #1699
Conversation
I use Debian Trixie AMD64 with XFCE 4.18. When I updated to version 1.83.1 and opened the program, all I saw was a mangled version of the interface without text. I tested various versions of VS Codium and VS Code to find when the issue originated, and found it started with Codium version 1.82 (didn't occur in 1.81.x, and couldn't replicate the bug in regular VS Code). I was about to file a bug report in this project when I found that the same issue was occurring upstream due to a Chromium, and thus Electron update (see microsoft/vscode#190437). I found that it was an issue with Mesa GPU caching upon VS Code updates (as well as updates of some other Electron-based applications). The issue was solved by deleting the GPU cache (which would make sense why I couldn't replicate the issue in regular Code: since it was a new install, the GPU cache was also brand new). In case other people come across the same issue while using VSCodium, I would like this solution to be available in the documentation until the Electron bug is quashed.
|
It's already in Troubleshooting |
|
Instead, we should add a link to the wiki page. |
|
I'll make that revision to the patch when I have the time. |
|
@266-750Balloons I've reused your text in the wiki since it make things clearer. Thx For the |
|
@GitMensch @PalinuroSec @paulcarroty Should the |
|
AFAIR Wiki access isn't flexible yet - rw access for all or only for maintainers, I don't like it. |
|
@paulcarroty Very true. Like in the current case, @266-750Balloons doesn't get the credit for the text that I have copied from his PR. Maybe, everything should be moved to the |
and then it's possible to generate a static doc website using something like mdBook. |
|
@266-750Balloons If you can update your PR and add your text to the file |
Since VSCode/Codium 1.82.x, the Linux version, upon package updates, may open up to a mangled version of the interface missing text, making it completely unusable. This is an upstream Electron/Chromium issue with Mesa shaders (see microsoft/vscode#190437).
A work-around suggested in that issue is to delete the GPU cache with the following command:
rm -rf ~/.config/VSCodium/GPUCacheIn case other users come across the same issue, I think it would be a good idea to address this in VSCodium documentation. It could be removed once the aforementioned bugs are fixed.