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
{{ message }}
Repository navigation
localhost relay (wslrelay) stalls permanently and leaks the connection when the Windows client pauses reading while still writing #42253
On Windows, connect to 127.0.0.1:18999. Read for 3 s while a second thread keeps writing 4 KB every 1 ms; stop reading for 20 s (keep writing); then try to read for 10 s; then close:
Check sockets on both sides (Windows: Get-NetTCPConnection -RemotePort 18999; WSL: ss -tn "( sport = :18999 or dport = :18999 )").
Expected Behavior
After the client resumes reading, data flows again in both directions. After the client closes, the relay closes its WSL-side connection.
Actual Behavior
After the pause, the client receives ~1.4 MB, then nothing (recv timeout); its writes also stall.
After close, the Windows socket stays in FIN_WAIT_1 and the relay's WSL-side socket stays ESTABLISHED with unread data, indefinitely (unchanged after 60 s+):
Without client writes during the pause (read-only client), the same test recovers fine.
In a real workload (MQTT client on Windows, broker in WSL Docker), this accumulated 192 leaked relay connections holding 573 MB of unread data and caused repeated keepalive timeouts until wsl --shutdown.
After this, port forwarding for that port is broken for new connections as well: wslrelay accepts the
connection on Windows (127.0.0.1:18999, state Established, owned by wslrelay), but nothing is forwarded to
the WSL listener (the server never sees an accept; no new socket in ss), and the client receives no data.
Connecting to the same server from inside WSL works immediately.
The leaked connection was still present 13+ minutes later (Windows FIN_WAIT_1, WSL-side ESTAB with 1.7 MB Recv-Q).
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
Activity
github-actions commentedon Nov 12, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
Yamahari commentedon Nov 12, 2026
no logs
chemwolf6922 commentedon Nov 13, 2026
Hi Yamahari .
This issue should be fixed with this PR #41458 and it's Linux part. The PR is currently in review.