NousResearch/hermes-agent

Gateway starvation from leaked background subprocesses

Cluster 76115. Data as of

Nothing open on GitHub. Fix merged in #76687. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #76687. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #76687. That is separate from the fix event.
Still open
Nothing open on GitHub.

An abandoned agent turn fails to clean up its background subprocesses, causing unbounded memory growth in the gateway cgroup and event loop starvation. The associated fixes scope subprocess reaping to only those created by the abandoned turn.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #76687 fix(gateway): reap only the background processes an abandoned turn created

    merged to main

    files: gateway/platforms/api_server.py, gateway/run.py, gateway/turn_context.py, tests/gateway/test_abandoned_turn_process_cleanup.py, tests/gateway/test_api_server.py, tests/gateway/test_tool_response_drop_recovery.py, tests/tools/test_process_registry.py, tools/process_registry.py

3 PRs closed without merging

From the close comments: duplicate 2 · merged via another change 1

  • #76172 fix: reap stale background processes to prevent gateway starvation (#76115) · duplicate → #76188, #76183
  • #76183 fix: reap stale background processes to prevent gateway starvation (#76115) · duplicate → #76188, #76172
  • #76188 fix(gateway): reap only the background processes an abandoned turn created · merged via another change → 80e4fb5, a356917, 1b88682, #76687
Closed issues · 1
  • Closed#76115Abandoned agent turn leaks its background subprocess (e.g. next build) unbounded → gateway cgroup hits MemoryHigh, event loop starves, all platforms/crons time out
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#76687
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
2 Aug 2026

For your agent

The same facts, typed.