Bug Report: some processes still do not terminate after closing terminal

[andrewbaker-uk]

Environment

Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): 0.2.1715.0

Any other software?

Steps to reproduce

Run ping across multiple powershell tabs and close terminal without stopping ping

Check taskmgr and ping.exe will still be running

Expected behavior

Ping.exe terminates when terminal session ends

Actual behavior

Terminal not killing processes executed after being closed

[Shorotshishir]

Could recreate it inside terminal and cmd does the same as PowerShell

• both CMD and Powershell tab hangs up for quite a long time if trying to close the tab without manually terminating the process, sometimes crashes the terminal app.
• If checked in Task Manager, we see the Ping and Powershell running, though the app has crashed.

[fredless]

have observed cmd+ping still running as well, though I cannot replicate reliably nor do I recall an associated crash or slow close as @Shorotshishir mentioned.

..and a packet trace confirms that the process is still sending traffic as you might expect.

EDIT in case it's helpful: just noticed that terminating the subprocess (ping in this case) when in this condition seems to allow cmd.exe to wrap up as well

[DHowett-MSFT]

So, this is weird. We stuff the shell and console host into a job object so they terminate when we do. That's a system feature that should almost certainly not fail.

[ShadowJonathan]

I also see this behaviour happen with WSL terminals, in ubuntu i can see multiple instances of init running after i closed their tabs, with their processes running in them.

(i discovered this because apt locked itself up while it waited for a nonexistent user confirmation while i got bounced trying to run an install from another tab, while the apt command already should've terminated a few hours ago when i closed that window)

[zadjii-msft]

#2185 Is probably related

[DHowett-MSFT]

Let's use #2185 as the master issue for these.