MCP orphan reaper PGID recycling safety fixes
Cluster 43044 · gateway. Data as of
Nothing open on GitHub. Fix merged in #131910 on 3 Oct 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 #131910. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131910. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the orphan MCP process reaper could send SIGTERM to unrelated processes if a process group ID (PGID) was recycled by the OS. The work involves adding per-process PID isolation, PGID ownership re-validation, and guards against this unsafe kill behavior.
Open issues0
Open PRs0
Fixes on record
-
#131910 fix(mcp): re-validate PGID ownership before killing orphaned process groups [risk 0.20]
files:
tests/tools/test_mcp_stability.py,tools/environments/local.py,tools/mcp_tool_lifecycle.py,tools/mcp_tool_transport.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · other 1
Closed issues · 1
- Closed#43044Gateway orphan-MCP reaper can SIGTERM an unrelated process via a recycled PGID
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
- gateway
- Merged PRs
- #131910
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 3 Oct 2026