From aa709a73a56324d85c9a5f97296bcc10660c5454 Mon Sep 17 00:00:00 2001 From: Som Date: Wed, 12 Aug 2026 12:24:16 +0000 Subject: [PATCH] doc: clarify signal listener behavior --- doc/api/process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/api/process.md b/doc/api/process.md index fe5ecbd3d45b..6104ea933c18 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -669,7 +669,8 @@ process.on('SIGTERM', handle); * `'SIGTERM'` and `'SIGINT'` have default handlers on non-Windows platforms that reset the terminal mode before exiting with code `128 + signal number`. If one of these signals has a listener installed, its default behavior will be - removed (Node.js will no longer exit). + removed. Signal events are emitted asynchronously, so Node.js may exit before + the listener is called if the event loop is otherwise empty. * `'SIGPIPE'` is ignored by default. It can have a listener installed. * `'SIGHUP'` is generated on Windows when the console window is closed, and on other platforms under various similar conditions. See signal(7). It can have a