Using the Kill Terminal icon fails to end running processes

[kenlyon]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.99.1
• OS Version: Windows 11 Enterprise, 24H2

1. Open a project in VS Code that has the ability to run a web server via an npm script, using something like vite for example.
2. Open the terminal in VS Code and run the command to start the web server. (In my case it's "yarn start".) Confirm in your browser that the site is running. (Mine was on http://localhost:3000)
3. Use the "Kill Terminal" icon (garbage can) to kill the terminal.
4. Attempt to reload the page in your browser.

Expected:

An "Unable to connect" error (or similar) indicating the site is no longer running.

Actual:

The site continues to work. In fact, even exiting out of VS Code does not terminal the process. I closed every window in my computer and it still ran.

Workaround:

If you have npm installed, you can run this command:

npx kill-port 3000

Alternatively, you can use Task Manager to locate node.exe and kill it. (There were several processes in my case.)

Additional Info:

I only started to see this after upgrading to Windows 11. It is also a new machine.

[rgbjoy]

I swear this is new and I've only started noticing too.