github-actions[bot]
commented
1 month ago 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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.View similar issues
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Closed similar issues:
- WSL1 many wsl.exe instances persist after wsl.exe --shutdown (#6600), similarity score: 0.74
- Running
wsl.execauses "Application Info"/appinfoservice to leak ~5 registry handles. Turns into a very steady leak with Docker Desktop. Hundreds of thousands of handles leaked after a week uptime. (#9851), similarity score: 0.74 - Memory Leak / Thousands of abandoned wsl.exe instances (WSL Preview) (#8703), similarity score: 0.72
- Unable to connect to existing WSL instance because socket already exists in /run/WSL (#7252), similarity score: 0.71
- WSL 2: Cannot launch detached/immune to hangups (nohup ... &) processes from wsl-command (#5143), similarity score: 0.70
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
iongion
Windows Version
Microsoft Windows [Version 10.0.22631.4317]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-microsoft-standard-WSL2
Distro Version
Ubuntu 24.04
Other Software
I am using a custom application, developed by myself - https://container-desktop.com
Because on Windows, I cannot use WSL 2 unix domain sockets directly, I need to relay them somehow. My choice is to use
socatbinary in Ubuntu and use stdin and stdout to relay from a unix socket,/var/run/docker.sockI created a nodejs server that listens to a named pipe and spawns socat processes inside WSL to write to the socket and read back from it. My invocation arguments for spawning the WSL socat binary look like this:After several calls, I see a lot of these accumulating
And behind each are various like these
In linux,
ps auxshows thatsocatis dead, but a lot of these accumulatedRepro Steps
clientSocketProcess.kill()in nodejsYou will notice, socat is killed in WSL, but the weird wsl wrappers are still there and keep accumulating.
Expected Behavior
I expect the related processes to die once the linux socat has exited.
Actual Behavior
Too many init processes running in WSL distro and also too many
wslhost.exeandconhost.exepairsDiagnostic Logs
WslLogs-2024-10-12_21-18-45.zip