- Notifications
You must be signed in to change notification settings - Fork35
Open
Description
Timeline of Events
- 07:01:57 - Extension Host Process exited normally (code: 0)
- 07:02:27 - ManagementConnection disconnected, 3-hour reconnection timeout starts
- 08:57-09:02 - Multiple "CSRF token not found" errors from Coder extension
- 09:02:16 - Critical failure sequence:
• Socket timeout after 20 seconds (unacknowledgedMsgCount: 17)
• Attempted reconnection
• resolveAuthority(ssh-remote) returned an error after 1 ms Cannot resolve authority
• Permanent error - connection given up
Root Cause Analysis:
Primary Issue: Coder Extension Local Host Crash
The local extension host (PID 29360) terminated at 09:01:56, which killed all local extensions including the Coder extension that manages remote authority resolution.When VS Code tried to reconnect at 09:02:16, it called resolveAuthority(ssh-remote) but the extension was already dead, causing instant failure.Secondary Issues:
- CSRF token errors - Repeated failures from the Coder extension (lines 64, 72, 236, 482, 483, 1044, 1290, 1291)
- Navigator deprecation warnings - PendingMigrationError spam (not critical but noisy)
Why Language Features Break:
From the logs at 09:02:16:
Error: Unable to read file 'vscode-remote://.../.vscode/settings.json' (Canceled: Canceled)Error: Unable to read file 'vscode-remote://.../.vscode/tasks.json' (Canceled: Canceled)Error: Unable to read file 'vscode-remote://.../.vscode/launch.json' (Canceled: Canceled)Full logs here:https://gist.github.com/ericpaulsen/1cacac3145384f2b1ea1c11be0b08d60
When the connection dies:
- All file system operations are canceled
- Language servers lose their connection to workspace files
- Extensions can't read configuration
- IntelliSense, linting, navigation all fail
Recommendations:
Immediate:
- File issue for Coder extension stability - The local extension host should not be crashing. The CSRF token errors suggest authentication/session management bugs
- Check for Coder extension updates - Logs show v1.11.3 with navigator deprecation warnings
Workarounds for users:
- Keep VS Code window focused when possible (reduces suspend/resume issues)
- Use "Remote-SSH: Kill VS Code Server on Remote" then reconnect (cleaner than window reload)
- Consider web VS Code for critical work
Investigation needed:
- Why is the Coder extension repeatedly failing CSRF token validation?
- Why did the local extension host terminate at 09:01:56?
- Is there a memory leak or resource exhaustion pattern?
Metadata
Metadata
Assignees
Labels
No labels