Kill orphaned subprocess after post-spawn setup error
Cluster 2749 · environments. Data as of
Nothing open on GitHub. Fix merged in #22850 on 10 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #22850. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #22850. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where a spawned subprocess (Popen) is left orphaned if setup steps after spawning encounter errors. The fixes ensure the process is killed in that error path to prevent resource leaks.
Open issues0
Open PRs0
Fixes on record
-
#22850 fix(process_registry): kill orphaned Popen on post-spawn setup failure (salvage #22628)
files:
tests/tools/test_process_registry.py,tools/process_registry.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#2749[Bug]: Subprocess leak on post-Popen setup failure in process_registry
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- environments
- Merged PRs
- #22850
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 10 May 2026