Disable GPU acceleration to fix the immediate problem. Deep dive into GPU rendering errors to solve the underlying problem.
If GPU acceleration fucks up, there’s a good chance it’s not just VS Code is being affected. I get this sometimes after I update my Nvidia drivers, and some applications struggle to use Vulkan in Wayland on Nvidia (on Gnome). I had to switch back to X11 on my desktop to make browsers and other GPU accelerated programs behave normally, because software rendering was eating up CPU cores for no reason.
If you’ve just updated your firmware or drivers, a reboot may help. Disabling the GPU through either config flags or command line parameters will make the text appear, but it’ll also cost you more CPU cycles (and battery life, if you’re on a laptop).
I am on X11. rebooting, reinstalling and code--disable-gpu didn’t help. Only deleting the config files.
However, reading other comments it seems code--disable-gpu seems to work for most folks.
Disable GPU acceleration to fix the immediate problem. Deep dive into GPU rendering errors to solve the underlying problem.
If GPU acceleration fucks up, there’s a good chance it’s not just VS Code is being affected. I get this sometimes after I update my Nvidia drivers, and some applications struggle to use Vulkan in Wayland on Nvidia (on Gnome). I had to switch back to X11 on my desktop to make browsers and other GPU accelerated programs behave normally, because software rendering was eating up CPU cores for no reason.
If you’ve just updated your firmware or drivers, a reboot may help. Disabling the GPU through either config flags or command line parameters will make the text appear, but it’ll also cost you more CPU cycles (and battery life, if you’re on a laptop).
I am on X11. rebooting, reinstalling and
code --disable-gpudidn’t help. Only deleting the config files. However, reading other comments it seemscode --disable-gpuseems to work for most folks.