Verified Solution[microsoft/vscode] debugger crashed somehow, know isn't able to get removed have to reinstall
Sponsored Content
### ROOT CAUSE
The crash is likely caused by an incompatible extension, corrupted VS Code data, or a conflict with the macOS system or hardware (Apple M1 Pro). The debugger process may be hanging or crashing due to an extension issue, and the inability to close it suggests a deeper system-level conflict or corruption in VS Code's core processes.
### CODE FIX
1. **Run VS Code in Safe Mode**: Hold `Cmd + Shift` while launching VS Code to disable extensions. If the crash does not occur, an extension is the root cause.
- Update or disable extensions one by one to identify the culprit.
2. **Reset VS Code User Data**: Delete corrupted configuration files:
- Close all instances of VS Code.
- Move the `~/Library/Application Support/Code` folder to your Desktop.
- Restart VS Code to reset settings and extensions.
3. **Update macOS and VS Code**: Ensure your macOS (arm64) and VS Code are updated to the latest versions. Check for Metal graphics driver updates in System Settings > About This Mac > System Report.
4. **Check for Known Issues**: Compare your system configuration with [VS Code's release notes](https://github.com/microsoft/vscode/releases) for known M1 Pro compatibility issues.
5. **Reinstall with Clean State**: If all else fails, perform a clean reinstall by deleting the `~/Library/Application Support/Code` folder before reinstalling.
Deploy on DigitalOcean ($200 Credit)
Related Fixes
[tensorflow/tensorflow] Call for contributors for the upcoming 3.0 release documentation
[golang/go] internal/strconv: unrecognized failures
[microsoft/vscode] Critical performance issues with Copilot Chat – Credits wasted due to freezing