nodemon -v
: 8.11.3node -v
: 1.18.3nodemon -v app.js --development-mode
Detached child processes should survive a nodemon reset, just as they would survive a CTRL+C.
Detached child processes are killed on reset. If that child process happens to be a java process the app directory will also get spammed with hs_err_pidxxxx.log files that indicate SIGSEGV
errors. Example:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000000010da86c68, pid=13670, tid=0x0000000000000307
rs
Note: I don't believe this issue exists on windows.
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3
I don't believe this is stale since it hasn't been interacted by the owner or any maintainers in the timeframe.
@alallier I'm all the maintainers and owner. I don't have a solution, and so it's stale as no one has come forth.
Can @Autre31415 provide parred down code to replicate? I'm not sure this is fixable (again, since no one has offered any solution), as nodemon is doing exactly what it's supposed to do (end all the subprocesses).
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3
Most helpful comment
I don't believe this is stale since it hasn't been interacted by the owner or any maintainers in the timeframe.