port 8000 on localhost remains busy after gatsby app crashes

[adriatic]

Going through the Gatsby tutorial I observed that I cannot rerun the application that failed:

I stopped the previously run app which was different only in having a syntax error, by issuing a Ctrl-C signal. Then I deleted the node_modules folder and yarn.lock. rerun npm install, followed by gatsby develop

$ gatsby develop

Something is already running at port 8000

√ Would you like to run the app at another port instead? ... no

Instead of accepting the offer to run the app a different port, which would result with the app running at 8001 - conflicting with Gatsby using this (8001) port for a different purpose, I did the following

λ netstat -ano | findstr :8000
  TCP    127.0.0.1:8000         0.0.0.0:0              LISTENING       27692
  TCP    127.0.0.1:51914        127.0.0.1:8000         TIME_WAIT       0

and then

taskkill /PID 27692 /F
SUCCESS: The process with PID 27692 has been terminated.

At this point, the app would run normally using port 8000.

Please note my real point is not to share a solution for a problem that should not take place if the Ctrl-C signal processing would do the cleanup I did manually (see above). Trying to stay as modest as I can, it is my perception that almost everyone gets trapped with this "port in use" issue, so I am surprised that such a problem still exists. I would rather believe I am somewhat confused and would really appreciate it if someone explains it to me.

[adriatic]

I encountered this problem using VSCode

Version: 1.55.2 (user setup)
Commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:35:57.887Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.19041

with the split console (bash and powershell)

Most of the time, the app behaves correctly - however, using the Ctrl-C to stop it the listener on port 8000 remains active.