microsoft / microsoft/vscode-remote-release
WSL 2 connection lost after too much time in Modern Standby
Open
@aeschli is already working on this.
Since Aug 1, 2020.
bug
plan-review
reconnecting
wsl
wsl-team-interest
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VS Code Version: 1.47.3
- Local OS Version: Windows 10 19042.421
- Remote OS Version: Ubuntu 18.04
- Remote Extension/Connection Type: WSL
Steps to Reproduce:
- Start WSL 2 on a device with Modern Standby, e.g. a Surface.
- Put the device into Modern Standby for several hours, e.g. overnight.
- Wake up the device after several hours, e.g. in the morning.
In the morning, VS Code says it's lost its connection with WSL and needs to reload the window. However, calling wsl -l -v shows that the WSL 2 VM is indeed still running.
I've written about Modern Standby specifically because I don't know if this behavior occurs with normal standby as well, but I imagine it's probably specific to Modern Standby because Windows is still active there, but not during normal standby afaik.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.