Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
devserver: ctrl+c does not always kill subprocesses
See original GitHub issuerunning
kolibri manage --debug devserver -- --webpack
and then Ctrl-c to quit.
Occasionally the node watch process remains running in the background, and changes to files will cause a re-build.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
can't close webpack-dev-server --progress with Ctrl + C
Running the dev server with: yarn webpack-dev-server --progress . I'm not including webpack configs since seems to be reproducing on a ...
Read more >bash - ctrl+c doesn't wait for child process (background ...
I have a script which registers a SIGINT trap and starts a ffmpeg background process that records part of the screen.
Read more >Pressing Ctrl-C stops bash script, but don't stop PHP script ...
If I call the bash script and press Ctrl + C at this time, while it's sleeping, it kills the bash script, but...
Read more >How to Deploy, Manage and Scale Node.js Apps with PM2
Go ahead and start the server for your application in development mode using the command below. Ensure to kill the previous instance with...
Read more >When The Webpack Dev Server Does Not Close It's Port
However, I have recently been experiencing more frequent occurrences where pressing Ctrl-C (^C) to stop the Webpack Dev Server integrated with ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think should have finally been resolved by #3360
I have, on occasion, but I think
killall nodeis the only surefire recourse.