Nodemon: detached child processes are killed when nodemon resets

Created on 27 Jul 2018  路  4Comments  路  Source: remy/nodemon

  • nodemon -v: 8.11.3
  • node -v: 1.18.3
  • Operating system/terminal environment: macOS iTerm2
  • Command you ran: nodemon -v app.js --development-mode

Expected behaviour

Detached child processes should survive a nodemon reset, just as they would survive a CTRL+C.

Actual behaviour

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

Steps to reproduce

  1. In macOS start up a node process in nodemon which spawns a detached child process.
  2. Reset by either editing a watched file or using rs

Note: I don't believe this issue exists on windows.

missing code to replicate stale

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.

All 4 comments

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dimsmol picture dimsmol  路  4Comments

olalonde picture olalonde  路  3Comments

endquote picture endquote  路  4Comments

binarykitchen picture binarykitchen  路  5Comments

maotora picture maotora  路  4Comments