Node.js processes *still* don't quit after stopping debugging

[casperOne]

Describe the bug

The same issue as #5204, many nodejs instances continue to run after debugging an ASP.NET Core application.

Currently, I am using taskkill.exe /F /IM node.exe /T to shut down instances after each debugging session to mitigate this. Here's a screenshot showing 18 nodejs processes running (all children of VS.NET) after debugging:

One (or more) of these is typically (but not always) consuming a large amount of CPU.

It tends to slow down performance on my machine quite a bit after this.

To Reproduce

This is an ASP.NET Core React SPA application that was created with the template ~ASP.NET Core 2.1. It's been upgraded over time and is currently on ASP.NET Core 5.0.

Debugging occurs in VS.NET 2022.

I do have a private github repo that I'm willing to share privately to assist.

[TanayParikh]

Hello @casperOne, thanks for contacting us. Are you still experiencing this issue in .NET 6?

Hi @casperOne. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[casperOne]

@TanayParikh Yes, after switching to 6.0, after going through two debug sessions, there were 13 nodejs processes that were hanging around.

[TanayParikh]

Hmm that's certainly strange. We've had issues with processes not being killed after debugging, but having 13 errant processes after just 2 debug session seems very odd.

Are you sure the processes are all being created by .NET / VS? Could you try using Proc Explorer to get an idea of the process hierarchy / tree?

Hi @casperOne. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[casperOne]

@TanayParikh I've looked into this more. While debugging, the process tree looks like this:

You can see that the node instances are children of iisexpress. The full command line of the cmd.exe process that controls the nodejs process is

"cmd" /c npm run start -- 

However, when I close the browser (effectively ending the debugging session), the cmd.exe (with the child nodejs processes) gets orphaned:

[TanayParikh]

Thanks @casperOne that's really helpful. Do you have a minimal, public, GitHub repro project that we could use to investigate further? Note we aren't able to use private repos