Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying #12159

iongion · 2024-10-12T19:11:40Z

Windows Version

Microsoft Windows [Version 10.0.22631.4317]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

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 socat binary in Ubuntu and use stdin and stdout to relay from a unix socket, /var/run/docker.sock
I 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:

 [
              "--distribution",
              "Ubuntu-24.04",
              "--exec",
              "socat",
              "-v",
              "-d",
              "-d",
              "-d",
              `UNIX-CONNECT:/var/run/docker.sock,retry,forever`,
              "STDIO"
]

After several calls, I see a lot of these accumulating

And behind each are various like these

In linux, ps aux shows that socat is dead, but a lot of these accumulated

root      342045  0.0  0.0   2320   144 ?        S    19:37   0:00 /init
root      342054  0.0  0.0   2320   144 ?        S    19:37   0:00 /init
root      342076  0.0  0.0   2320   144 ?        S    19:37   0:00 /init
root      342085  0.0  0.0   2320   144 ?        S    19:37   0:00 /init
root      342088  0.0  0.0   2320   144 ?        S    19:37   0:00 /init
root      342591  0.0  0.0   2320   144 ?        S    19:38   0:00 /init
root      342609  0.0  0.0   2320   144 ?        S    19:38   0:00 /init
root      342618  0.0  0.0   2320   144 ?        S    19:38   0:00 /init
root      342621  0.0  0.0   2320   144 ?        S    19:38   0:00 /init
root      342636  0.0  0.0   2320   144 ?        S    19:38   0:00 /init
root      342851  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342854  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342880  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342886  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342889  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342898  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342901  0.0  0.0   2320   144 ?        S    19:39   0:00 /init
root      342957  0.0  0.0   2320   144 ?        S    19:40   0:00 /init
root      342960  0.0  0.0   2320   144 ?        S    19:40   0:00 /init
root      343447  0.0  0.0   2320   144 ?        S    19:42   0:00 /init
root      343460  0.0  0.0   2320   144 ?        S    19:42   0:00 /init
root      343463  0.0  0.0   2320   144 ?        S    19:42   0:00 /init
root      343668  0.0  0.0   2320   144 ?        S    19:43   0:00 /init
root      343776  0.0  0.0   2320   144 ?        S    19:44   0:00 /init
root      343782  0.0  0.0   2320   144 ?        S    19:44   0:00 /init
root      344186  0.0  0.0   2320   144 ?        S    19:46   0:00 /init
root      344200  0.0  0.0   2320   144 ?        S    19:46   0:00 /init
root      344316  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344362  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344365  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344368  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344395  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344404  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344548  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344560  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344568  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344571  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344586  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344595  0.0  0.0   2320   144 ?        S    19:47   0:00 /init
root      344778  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344789  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344804  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344834  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344837  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344843  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344849  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344868  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344871  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344883  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      344901  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345063  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345117  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345120  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345123  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345133  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345136  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345145  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345148  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345151  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345229  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345232  0.0  0.0   2320   144 ?        S    19:48   0:00 /init
root      345235  0.0  0.0   2320   144 ?        S    19:48   0:00 /init

Repro Steps

Create a named pipe server and run it in nodejs (node.exe)
For each client connection, spawn a new socat process as above, bind to clientSocket data event and write the chunk to socat STDIN, read back from socat STDOUT and write the data to the clientSocket
Close the spawned socat process using clientSocketProcess.kill() in nodejs

You 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.exe and conhost.exe pairs

Diagnostic Logs

WslLogs-2024-10-12_21-18-45.zip

The text was updated successfully, but these errors were encountered:

github-actions · 2024-10-12T19:12:35Z

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:

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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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.exe causes "Application Info"/appinfo service 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 · 2024-10-12T19:16:57Z

I have attached the logs as instructed with the issue reproduced.

github-actions · 2024-10-12T19:17:43Z

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/17351199/WslLogs-2024-10-12_21-14-42.zip
.wslconfig found
	Custom kernel command line found: 'ipv6.disable=1 cgroup_no_v1=all'
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

github-actions · 2024-10-12T19:19:11Z

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

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:

Running wsl.exe causes "Application Info"/appinfo service 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.76
WSL1 many wsl.exe instances persist after wsl.exe --shutdown (#6600), similarity score: 0.74
Memory Leak / Thousands of abandoned wsl.exe instances (WSL Preview) (#8703), similarity score: 0.72
WSL2: wsl.exe hangs for 10s of minutes before working (#11067), similarity score: 0.71
Unable to connect to existing WSL instance because socket already exists in /run/WSL (#7252), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information

.wslconfig found
	Custom kernel command line found: 'ipv6.disable=1 cgroup_no_v1=all'
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

iongion · 2024-10-12T19:20:24Z

WslLogs-2024-10-12_21-18-45.zip

github-actions · 2024-10-12T19:27:06Z

Diagnostic information

.wslconfig found
	Custom kernel command line found: 'ipv6.disable=1 cgroup_no_v1=all'
Detected appx version: 2.1.5.0

github-actions · 2024-10-12T19:27:54Z

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/17351229/WslLogs-2024-10-12_21-18-45.zip
.wslconfig found
	Custom kernel command line found: 'ipv6.disable=1 cgroup_no_v1=all'
Detected appx version: 2.1.5.0

github-actions bot added the needs-author-feedback label Oct 12, 2024

microsoft-github-policy-service bot removed the needs-author-feedback label Oct 12, 2024

iongion changed the title ~~Spawned nodejs processes with wsl.exe are not dying~~ Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying Oct 12, 2024

github-actions bot added the needs-author-feedback label Oct 12, 2024

microsoft-github-policy-service bot removed the needs-author-feedback label Oct 12, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying #12159

Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying #12159

iongion commented Oct 12, 2024 •

edited

Loading

github-actions bot commented Oct 12, 2024

iongion commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

iongion commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying #12159

Spawned wsl.exe processes by a windows native nodejs child_process spawn command are not dying #12159

Comments

iongion commented Oct 12, 2024 • edited Loading

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

github-actions bot commented Oct 12, 2024

Logs are required for review from WSL team

View similar issues

Closed similar issues:

iongion commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

View similar issues

Closed similar issues:

iongion commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

github-actions bot commented Oct 12, 2024

iongion commented Oct 12, 2024 •

edited

Loading