Troubleshooting a VS Code Crash on Linux
The author encountered an issue where multiple instances of VS Code kept spawning on their Parrot OS machine, causing the system to freeze. They investigated the root cause and found it was due to a combination of factors, including GPU driver issues, lock file corruption, and session restore settings.
Why it matters
This article provides a detailed troubleshooting guide for a common issue faced by Linux users running Electron-based applications like VS Code, which can help others avoid similar system freezes and crashes.
Key Points
- 1VS Code crashed mid-session, leaving behind corrupted lock files
- 2The lock files caused VS Code to think another instance was running, triggering a warning dialog
- 3Session restore tried to reopen all previously open windows, exacerbating the issue
- 4GPU acceleration conflicts with Intel UHD 605 GPU and Mesa drivers on Debian-based Linux
- 5Containerd (Docker's container runtime) was also contributing to the problem
Details
The author used both Claude and ChatGPT to help diagnose the issue. They found that the root cause was a combination of factors, including a GPU driver issue with the Intel UHD 605 GPU and Mesa drivers on Parrot OS (a Debian-based Linux distribution), as well as lock file corruption and session restore settings in VS Code. The author provided a step-by-step guide to fix the issue, which involved killing all VS Code processes, removing lock and singleton files, clearing the cache (including the GPU cache), and disabling GPU acceleration permanently. They also learned that using multiple AI assistants can be a smart approach to troubleshooting complex problems.
No comments yet
Be the first to comment