bug: next server does not shut down correctly

[konstantinmuenster]

When I run next-banner locally, it seems like the server is not correctly shut down. When I run it again, it starts another server on port 3001 and I still see the old node process (for port 3000) in my activity monitoring.

Ohne.Titel.mp4

Don't know if this is a general issue or specific to me?

[alvarlagerlof]

I just noticed this myself recently too. My theory is that something changed with the threading model in Next.js. On my end it's just a child process and it seems unlikely that changed. I tried to debug for a few hours recently and was not able to shut it down (tried about five new ways), but I will give it a try again soon.