Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
doc: clarify text about process not responding
The existing text about processes not responding is unclear, at least to
me. Suggestions for clarification welcome, but I think the best thing
might be to state that the process may stop responding and leave it at
that. The explanantion (about asynchronous listeners) is not clear to
me. (Why would the fact that the listeners are asynchronous matter?) If
it's an unnecessary detail (as seems likely), let's remove it.

PR-URL: #36117
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
  • Loading branch information
Trott authored and BethGriggs committed Dec 15, 2020
1 parent dde727e commit 8a7c2b9
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions doc/api/process.md
Expand Up @@ -523,10 +523,8 @@ process.on('SIGTERM', handle);
* `'SIGSTOP'` cannot have a listener installed.
* `'SIGBUS'`, `'SIGFPE'`, `'SIGSEGV'` and `'SIGILL'`, when not raised
artificially using kill(2), inherently leave the process in a state from
which it is not safe to attempt to call JS listeners. Doing so might lead to
the process hanging in an endless loop, since listeners attached using
`process.on()` are called asynchronously and therefore unable to correct the
underlying problem.
which it is not safe to call JS listeners. Doing so might cause the process
to stop responding.
* `0` can be sent to test for the existence of a process, it has no effect if
the process exists, but will throw an error if the process does not exist.

Expand Down

0 comments on commit 8a7c2b9

Please sign in to comment.