Node process doesn't seem to be released after stopping asp.net core #1426

New Issue

fergalmoran · 2025-08-09T17:20:06Z

fergalmoran commented

2025-08-09 17:20:06 +00:00

Originally created by @asadsahi on 8/18/2016

I have observed both on windows 7 and windows 10 that if I run asp.net core spa generator multiple times, e.g start debug, stop, start debug, stop every time I run application it starts node instance and doesn't clean itself, which lead to unexpected behavior such as files are locked after asp.net process is stopped and caching old client files by node/webpack. I am not using any other node application and here is what process explorer looks like:

*Originally created by @asadsahi on 8/18/2016* I have observed both on windows 7 and windows 10 that if I run asp.net core spa generator multiple times, e.g start debug, stop, start debug, stop every time I run application it starts node instance and doesn't clean itself, which lead to unexpected behavior such as files are locked after asp.net process is stopped and caching old client files by node/webpack. I am not using any other node application and here is what process explorer looks like: ![image](https://cloud.githubusercontent.com/assets/3470892/17791780/0c7210e8-6595-11e6-8734-8c949572df97.png)

fergalmoran closed this issue

2025-08-09 17:20:06 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1426