Skip to content

Commit 142cacd

Browse files
Trottcodebytere
authored andcommitted
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>
1 parent 3d623d8 commit 142cacd

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

doc/api/process.md

+2-4
Original file line numberDiff line numberDiff line change
@@ -525,10 +525,8 @@ process.on('SIGTERM', handle);
525525
* `'SIGSTOP'` cannot have a listener installed.
526526
* `'SIGBUS'`, `'SIGFPE'`, `'SIGSEGV'` and `'SIGILL'`, when not raised
527527
artificially using kill(2), inherently leave the process in a state from
528-
which it is not safe to attempt to call JS listeners. Doing so might lead to
529-
the process hanging in an endless loop, since listeners attached using
530-
`process.on()` are called asynchronously and therefore unable to correct the
531-
underlying problem.
528+
which it is not safe to call JS listeners. Doing so might cause the process
529+
to stop responding.
532530
* `0` can be sent to test for the existence of a process, it has no effect if
533531
the process exists, but will throw an error if the process does not exist.
534532

0 commit comments

Comments
 (0)