René's URL Explorer Experiment


Title: `SIGTERM` killing an invalid `node:child_process` spawn terminates main process · Issue #65052 · nodejs/node · GitHub

Open Graph Title: `SIGTERM` killing an invalid `node:child_process` spawn terminates main process · Issue #65052 · nodejs/node

X Title: `SIGTERM` killing an invalid `node:child_process` spawn terminates main process · Issue #65052 · nodejs/node

Description: TipRewritten by @avivkeller Version v24.19.0, v26.6.0 Platform macOS Darwin Subsystem node:child_process What steps will reproduce the bug? Running .kill('SIGTERM') on an invalid child_process spawn results in the termination of the main...

Open Graph Description: TipRewritten by @avivkeller Version v24.19.0, v26.6.0 Platform macOS Darwin Subsystem node:child_process What steps will reproduce the bug? Running .kill('SIGTERM') on an invalid child_process spaw...

X Description: TipRewritten by @avivkeller Version v24.19.0, v26.6.0 Platform macOS Darwin Subsystem node:child_process What steps will reproduce the bug? Running .kill('SIGTERM') on an invalid child_proc...

Opengraph URL: https://github.com/nodejs/node/issues/65052

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`SIGTERM` killing an invalid `node:child_process` spawn terminates main process","articleBody":"> [!TIP]\n> Rewritten by @avivkeller\n\n### Version\n\nv24.19.0, v26.6.0\n\n### Platform\n\n```text\nmacOS Darwin\n```\n\n### Subsystem\n\n`node:child_process`\n\n### What steps will reproduce the bug?\n\nRunning `.kill('SIGTERM')` on an invalid `child_process` spawn results in the termination of the main Node.js process (the caller)\n\nFor instance, running `require('child_process').spawn('whoami').kill('SIGTERM');`.\n\n### How often does it reproduce? Is there a required condition?\n\nEvery time.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nNode.js should abort killing since `.pid` will be `0`.\n\n\u003cdetails>\n\u003csummary>Original Issue\u003c/summary>\n\n### Version\n\nv24.18.0\n\n### Platform\n\n```text\nmacOS Darwin\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nHi, \n\nI would like to report a bug that happens only on macOS. When run the code snippet below, the main process gets terminated: \n\n```javascript\nvar {spawn} = require('child_process');\n\nArray.prototype[Symbol.iterator] = function* () {};\nvar proc = spawn(\"ts-node\", [\"--version\"]); //or any other non-OS native command, e.g., brew --version  \nconsole.log(\"subprocess forked\");\nproc.kill('SIGTERM');\nconsole.log(\"Killed Subprocess\");\n```\n\n### How often does it reproduce? Is there a required condition?\n\nIt's a permanent effect \n\n### What is the expected behavior? Why is that the expected behavior?\n\nTo kill the child process only \n\n\n### What do you see instead?\n\nI get the following output: \n\n```shell\nsubprocess forked\nzsh: terminated  node test.js\n```\n\n### Additional information\n\n_No response_\n\n\u003c/details>","author":{"url":"https://github.com/vdata1","@type":"Person","name":"vdata1"},"datePublished":"2026-08-05T16:20:34Z","url":"https://github.com/nodejs/node/issues/65052"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:52a4fca9-f6dc-7fa7-49ff-0b69a6bba7ce
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id9B06:A2B38:463B6A:5AD1AF:6AED2258
html-safe-noncefd70b99485b90f834f3bc4f8c8844e6b35f186f71f9129415d58d832e6612376
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5QjA2OkEyQjM4OjQ2M0I2QTo1QUQxQUY6NkFFRDIyNTgiLCJ2aXNpdG9yX2lkIjoiMzYxNjU1MTA4MjgwOTY5Njg1NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmacb6cb52cbf039d3f997144dafd6561919d0775d2a234a51a91bfd54492d6bb46c
hovercard-subject-tagissue:5072996842
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/65052/issue_layout
twitter:imagehttps://opengraph.githubassets.com/14bcf40b84b2a4452bb4dcb052e91d2035ae5da52444dcd7493d5a52611989b9/nodejs/node/issues/65052
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/14bcf40b84b2a4452bb4dcb052e91d2035ae5da52444dcd7493d5a52611989b9/nodejs/node/issues/65052
og:image:altTipRewritten by @avivkeller Version v24.19.0, v26.6.0 Platform macOS Darwin Subsystem node:child_process What steps will reproduce the bug? Running .kill('SIGTERM') on an invalid child_process spaw...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamevdata1
hostnamegithub.com
expected-hostnamegithub.com
Nonee3e0f7f63e50c6fe879198a93a0a023a648ecc0a5e9bc3b5e033ac57172237e6
turbo-cache-controlno-preview
go-importgithub.com/nodejs/node git https://github.com/nodejs/node.git
octolytics-dimension-user_id9950313
octolytics-dimension-user_loginnodejs
octolytics-dimension-repository_id27193779
octolytics-dimension-repository_nwonodejs/node
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id27193779
octolytics-dimension-repository_network_root_nwonodejs/node
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release707a24b346ac8a82878b9c084efaa38a997660cb
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/nodejs/node/issues/65052#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fnodejs%2Fnode%2Fissues%2F65052
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fnodejs%2Fnode%2Fissues%2F65052
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=nodejs%2Fnode
Reloadhttps://github.com/nodejs/node/issues/65052
Reloadhttps://github.com/nodejs/node/issues/65052
Reloadhttps://github.com/nodejs/node/issues/65052
nodejshttps://github.com/nodejs
nodehttps://github.com/nodejs/node
Codehttps://github.com/nodejs/node
Issues657 (657)https://github.com/nodejs/node/issues
Pull requests666 (666)https://github.com/nodejs/node/pulls
Actionshttps://github.com/nodejs/node/actions
Projectshttps://github.com/nodejs/node/projects
Security and qualityhttps://github.com/nodejs/node/security
Insightshttps://github.com/nodejs/node/pulse
https://github.com/nodejs/node
New issuehttps://github.com/login?return_to=https://github.com/nodejs/node/issues/65052
New issuehttps://github.com/login?return_to=https://github.com/nodejs/node/issues/65052
#65054https://github.com/nodejs/node/pull/65054
SIGTERM killing an invalid node:child_process spawn terminates main processhttps://github.com/nodejs/node/issues/65052#top
#65054https://github.com/nodejs/node/pull/65054
https://github.com/vdata1
vdata1https://github.com/vdata1
on Aug 5, 2026https://github.com/nodejs/node/issues/65052#issue-5072996842
@avivkellerhttps://github.com/avivkeller
https://github.com/avivkeller
avivkellerhttps://github.com/avivkeller
on Aug 5, 2026https://github.com/nodejs/node/issues/65052#issuecomment-5195550177
avivkellerhttps://github.com/avivkeller
on Aug 5, 2026https://github.com/nodejs/node/issues/65052#event-29026319213
https://github.com/vdata1
vdata1https://github.com/vdata1
on Aug 6, 2026https://github.com/nodejs/node/issues/65052#issuecomment-5207347632
nodejs-github-bothttps://github.com/nodejs-github-bot
completedhttps://github.com/nodejs/node/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#65054https://github.com/nodejs/node/pull/65054
on Sep 12, 2026https://github.com/nodejs/node/issues/65052#event-31018399159
nodejs-github-bothttps://github.com/nodejs-github-bot
on Sep 12, 2026https://github.com/nodejs/node/issues/65052#event-31018399192
src: don't kill own process group on failed spawnhttps://github.com/nodejs/node/commit/ce20f7acb3f399eec45dacf8e46d94add36a7cc3
ce20f7ahttps://github.com/nodejs/node/commit/ce20f7acb3f399eec45dacf8e46d94add36a7cc3
aduh95https://github.com/aduh95
on Sep 16, 2026https://github.com/nodejs/node/issues/65052#event-31270403297
src: don't kill own process group on failed spawnhttps://github.com/nodejs/node/commit/4141e2260601f45de5f4f28c020c12bc38e265fd
4141e22https://github.com/nodejs/node/commit/4141e2260601f45de5f4f28c020c12bc38e265fd
src: don't kill own process group on failed spawnhttps://github.com/nodejs/node/commit/6229af3997c1d1e7bf8074ccbe2cc35830e58916
6229af3https://github.com/nodejs/node/commit/6229af3997c1d1e7bf8074ccbe2cc35830e58916
src: don't kill own process group on failed spawnhttps://github.com/nodejs/node/commit/70117640f7850da8fda7a42b6f671672535eac90
7011764https://github.com/nodejs/node/commit/70117640f7850da8fda7a42b6f671672535eac90
devxoulhttps://github.com/devxoul
on Oct 20, 2026https://github.com/nodejs/node/issues/65052#event-33709436418
fix: never signal a child whose spawn failed (code-yeongyu#3706)https://github.com/devxoul/senpi/commit/e3ef96325d47b54bdf650dbe04cb8d248ccdc526
code-yeongyu#3706https://github.com/code-yeongyu/senpi/issues/3706
e3ef963https://github.com/devxoul/senpi/commit/e3ef96325d47b54bdf650dbe04cb8d248ccdc526
Sign up for freehttps://github.com/signup?return_to=https://github.com/nodejs/node/issues/65052
Sign in to commenthttps://github.com/login?return_to=https://github.com/nodejs/node/issues/65052
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.