René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SIGTERM handler does not run if there are no tasks running and exit code is always 0","articleBody":"\u003c!--\r\nThank you for reporting a possible bug in Node.js.\r\n\r\nPlease fill in as much of the template below as you can.\r\n\r\nVersion: output of `node -v`\r\nPlatform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)\r\nSubsystem: if known, please specify the affected core module name\r\n\r\nIf possible, please provide code that demonstrates the problem, keeping it as\r\nsimple and free of external dependencies as you can.\r\n-->\r\n\r\n* **Version**: v11.15.0\r\n* **Platform**: Linux tsundberg-dev 4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux\r\n* **Subsystem**: process\r\n\r\n\u003c!-- Please provide more details below this comment. -->\r\n---\r\nTo run the following tests paste them into `index.js` and run `node index.js; echo $?`\r\n\r\n---\r\n#### Case 1\r\nThe following results in an expected output:\r\n```node\r\nprocess.kill(process.pid, 'SIGTERM')\r\n```\r\nOutput:\r\n```\r\nTerminated\r\n143\r\n```\r\n---\r\n#### Case 2\r\nAdding a SIGTERM results in an exit code of 0, and the handler never runs:\r\n```node\r\nprocess.on('SIGTERM', () => {\r\n    console.error('Handle ran!')\r\n    process.exit(1)\r\n})\r\n\r\nprocess.kill(process.pid, 'SIGTERM')\r\n```\r\nOutput:\r\n```\r\n0\r\n```\r\n---\r\n#### Case 3\r\nAdding a timeout or some other task that keeps node alive results in the expected behavior:\r\n```node\r\nprocess.on('SIGTERM', () => {\r\n    console.error('Handle ran!')\r\n    process.exit(1)\r\n})\r\n\r\nprocess.kill(process.pid, 'SIGTERM')\r\n\r\nsetTimeout(() => {}, 100000)\r\n```\r\nOutput:\r\n```\r\nHandle ran!\r\n1\r\n```","author":{"url":"https://github.com/TrevorSundberg","@type":"Person","name":"TrevorSundberg"},"datePublished":"2019-07-01T23:10:52Z","url":"https://github.com/nodejs/node/issues/28502"}