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
Mirrored networking: init's bind() interceptor stalls bind() ~600 s, grows to 12+ GB and is OOM-killed; bind() then returns ENOSYS until wsl --shutdown #42322
A Python 3 service that opens many short-lived outbound connections (ODBC Driver 17 for SQL Server to Azure SQL, plus HTTPS). Each new SQL login calls bind() on an ephemeral port.
Repro Steps
.wslconfig:
[wsl2]
networkingMode=mirrored
Start WSL and run a workload that makes repeated outbound TCP connections which bind() first (here: pyodbc / msodbcsql17 (ODBC Driver 17 for SQL Server) logins to Azure SQL, roughly one every 10–20 s).
After a few minutes to about an hour, bind() calls start to stall.
Expected Behavior
bind() on an ephemeral port returns immediately, and WSL's init keeps a stable memory footprint.
Actual Behavior
Seen on 2026-10-21 and again on 2026-11-21. In both cases:
bind() calls stall. On 2026-10-21, five stalled binds were released together exactly 600 s after the first stall.
PID 226 (init, the mirrored-networking interceptor) grows without bound until the kernel OOM-kills it:
2026-10-21: logged __vm_enough_memory allocation failures at 12:10:48 (exactly 600 s after a stalled bind), then was killed at 12:22:10 at 9.3 GB.
2026-11-21 09:48:37: killed with total-vm 16.0 GB, anon-rss 12.4 GB; swap was exhausted (Free swap 0 kB of 4 GB). The trigger was planned-stop-wa invoked oom-killer.
From then on, every bind() returns ENOSYS (38) until wsl --shutdown, including WSL's own interop: WSL (2 - init-systemd(Ubuntu-24.04)) ERROR: UtilBindVsockAnyPort:322: bind failed 38. Plain connect() without an explicit bind (HTTP, DNS) keeps working.
After wsl --shutdown it works again, then recurs (once within 25 minutes of a restart).
Key kernel lines (2026-11-21):
Nov 21 09:48:37 kernel: planned-stop-wa invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=200
Nov 21 09:48:37 kernel: Free swap = 0kB
Nov 21 09:48:37 kernel: Total swap = 4194304kB
Nov 21 09:48:37 kernel: [ 226] 0 226 4195142 3101411 3100829 0 582 32444416 940544 0 init
Nov 21 09:48:37 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=init,pid=226,uid=0
Nov 21 09:48:37 kernel: Out of memory: Killed process 226 (init) total-vm:16780568kB, anon-rss:12403316kB, file-rss:0kB, shmem-rss:2328kB, UID:0 pgtables:31684kB oom_score_adj:0
Nov 21 10:12:28 WSL (2 - init-systemd(Ubuntu-24.04)) ERROR: UtilBindVsockAnyPort:322: bind failed 38
The full kernel log from 09:30 to 09:50 is in the first comment below.
Diagnostic Logs
Kernel log (2026-11-21 09:30–09:50): in the first comment below. Networking logs from collect-wsl-logs.ps1 -LogProfile networking will be attached in a comment.
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'.
Kernel log from 2026-11-21 09:30–09:50, covering the OOM kill of init (PID 226) at 09:48:37, plus the first interop bind failed 38 line at 10:12:28. Hostname redacted.
I can't provide the collect-wsl-logs.ps1 output: this is a company-managed device, and I don't have an administrative PowerShell.
Here is what I can provide without admin rights; I'm happy to supply more on request:
The kernel log around the OOM kill of init (comment above).
wsl --version (2.7.10.0), the Windows build (10.0.26100.9911) and .wslconfig (only networkingMode=mirrored), all in the issue body.
A reproduction: the wedge recurs within minutes to an hour of wsl --shutdown under a workload of repeated SQL logins. I can run any non-admin command or capture during the next occurrence (for example journalctl, /proc/<pid>/status of init as it grows, or ss/dmesg snapshots).
Activity
github-actions commentedon Nov 21, 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'.
bpp-incom commentedon Nov 21, 2026
Kernel log from 2026-11-21 09:30–09:50, covering the OOM kill of
init(PID 226) at 09:48:37, plus the first interopbind failed 38line at 10:12:28. Hostname redacted.journalctl -k, 09:30–09:50 (148 lines)
Logs from
collect-wsl-logs.ps1 -LogProfile networkingwill follow, captured during the next occurrence.bpp-incom commentedon Nov 21, 2026
I can't provide the
collect-wsl-logs.ps1output: this is a company-managed device, and I don't have an administrative PowerShell.Here is what I can provide without admin rights; I'm happy to supply more on request:
init(comment above).wsl --version(2.7.10.0), the Windows build (10.0.26100.9911) and.wslconfig(onlynetworkingMode=mirrored), all in the issue body.wsl --shutdownunder a workload of repeated SQL logins. I can run any non-admin command or capture during the next occurrence (for examplejournalctl,/proc/<pid>/statusofinitas it grows, orss/dmesgsnapshots).