Ctrl-C leaves process running

[rhpijnacker]

When I start Intern with e.g. the BrowserStack tunnel and I use ctrl-c to stop Intern, then the tunnel processes are cleaned up properly, but the node process itself stays running.

[jason0x43]

What OS does this happen on and with which version of Node?

[rhpijnacker]

I happens on Windows 10 with Node v10.15.1 and MacOS with Node v12

[jason0x43]

Which node process is left running? I mean, dies the CLI interface die, dropping you back at a prompt, or does Intern just keep running?

[rhpijnacker]

When I start npm run intern config=... and then Ctrl-C, I get back to the command prompt, then the tunnel child processes are still running when using a Selenium tunnel. For BrowserStack it does cleanup the child processed. In any case the node process is still running (and keeping the port locked, which is why I noticed).
Could it be that it does not shut down the webserver properly?

All this on Windows 10, node v10.15.1

[jason0x43]

Which port is locked? 9000 (or whatever is being used for Intern's server)?

[jason0x43]

I've seen this when running dev Intern via npx, but only when a tunnel is active.

[jason0x43]

(And I forgot to mark this as a bug)