You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.CPU-20250213T214422.984Z.cpuprofile.txt
The text was updated successfully, but these errors were encountered: