From 8938d37251d3a48686825b477339ca3991a9d37b Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sat, 14 Nov 2020 06:59:58 -0800 Subject: [PATCH] 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: https://github.com/nodejs/node/pull/36117 Reviewed-By: Luigi Pinca Reviewed-By: Antoine du Hamel --- doc/api/process.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/api/process.md b/doc/api/process.md index d368b0aa573fa8..5665deab898573 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -525,10 +525,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.