Skip to content
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

VSCode Dev Container Crashes (Error: spawn UNKNOWN) or Opens Extremely Slow #10704

Open
KenHynes-pgmr opened this issue Feb 13, 2025 · 0 comments
Assignees
Labels
containers Issue in vscode-remote containers

Comments

@KenHynes-pgmr
Copy link

The Dev Container takes a considerable amount of time to open from a WSL instance (5-10 minutes) or it crashes on startup with a "spawn: UNKNOWN" error. The Container can be opened from a WSL instance when opened and rebuilt without cache, but any other configuration leads to a crash. When it does open, it is extremely slow to build as stated before. I have run code --status to confirm that extensionHost is not utilizing a significant amount of memory (pictured below) and I have confirmed with Extension Bisect that the issue is with Microsoft's Dev Container extension. Also attached below is the CPU profile recording of the extension crash. I would greatly appreciate any assistance with this matter.

Image

Image

CPU-20250213T214422.984Z.cpuprofile.txt

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants