P1 Tool Execution Spawns 1,100+ Bash Processes on Windows Desktop — Exhausts RAM, Freezes System (#54744)
Executive Summary
On Hermes Desktop for Windows, any command that triggers tool or shell execution spawns a continuously growing number of "Git for Windows" / Bash processes. In one documented test: 388 processes using 2.6 GB RAM → 1,100+ processes using ~16 GB RAM. Total system memory hit >80%, computer became almost unusable. Only recovery: terminate the Git for Windows process tree or restart. This is the 5th distinct Windows Desktop reliability bug we've tracked — two of which were opened on consecutive days.
Reproduction & Root Cause
Steps to Reproduce
- Open Hermes Desktop on Windows 11
- Start a new conversation
- Issue a simple command: "Create a new folder on the desktop and set up a new Next.js project named Test"
- Hermes executes
node --version,test -d,if [ -e ...], etc. - Open Task Manager
- Observe unbounded process growth
The Cascade
| Stage | What Happens |
|---|---|
| 1. Shell Spawn | Shell processes spawn for each tool execution step |
| 2. No Reuse | Processes are never reused or terminated — each new tool call spawns fresh processes |
| 3. No Enforcement | No max-concurrent-execution enforcement; no process-spawning loop detection |
| 4. Stuck Phase | Hermes gets stuck in the tool execution phase, unable to proceed or clean up |
| 5. System Freeze | Windows becomes completely unresponsive as RAM is exhausted |
Impact Assessment
| Dimension | Severity | Detail |
|---|---|---|
| System Stability | CRITICAL | Unbounded process explosion freezes the entire Windows system — not just Hermes, but the entire OS becomes unresponsive |
| Resource Exhaustion | CRITICAL | 16+ GB RAM consumed by leaked processes — exceeds the RAM capacity of most consumer laptops |
| Default Use Case | CRITICAL | Tool execution is the core value proposition of an agent — this bug makes the Desktop app unusable for its primary purpose |
| Recovery Difficulty | HIGH | Only recovery is manual process tree termination or system restart — no graceful degradation |
| Fix Complexity | HIGH | Requires process lifecycle management, max-concurrent-execution limits, and spawn-loop detection in the Electron shell layer |
Windows Desktop Bug History (5 Distinct Issues)
| Issue | Severity | Date | Description |
|---|---|---|---|
| #46260 | P2 | — | Installer fails at desktop stage (npm EBADENGINE) |
| #50897 | P2 | — | Desktop won't launch on Windows |
| #53069 | P2 | — | Missing simple-git module after upgrade |
| #54303 | P2 | Jun 28 | Desktop app leaks "Gt for Windows" processes while idle — continuous growth, high CPU |
| #54744 | P1 | Jun 29 | Tool execution spawns 1,100+ Bash processes, exhausts RAM, freezes system |
🔴 Pattern: Five distinct Windows Desktop reliability bugs across installation, launch, module resolution, idle process management, and catastrophic tool-execution process explosion. The last two were opened on consecutive days (June 28 and June 29). Windows Desktop reliability now has five independent failure modes — the Electron/Windows integration layer needs systematic hardening, not point fixes. Each fix addresses one failure mode while others proliferate.
Source Evidence
- GitHub Issue: #54744 — Tool Execution Spawns Hundreds/Thousands of Bash Processes on Windows Desktop
- Opened: June 29, 2026
- Reporter: @andreimironstv
- Labels: P1, backend/local, bug, comp/desktop, platform/windows, sweeper:risk-platform-windows, tool/terminal, type/bug
- System: Windows 11 Home N 24H2, Ryzen 3 3100, 32GB RAM, RX 6700 XT (12GB)
- Hermes: v0.17.0 | Python: 3.11.9
- Reporter willing to submit PR: Yes
- Debug artifacts: Full report + agent.log + gui.log + desktop.log + Task Manager screenshots provided
📋 https://hermes-agent.reviews/hermes-tool-execution-bash-process-explosion-54744.html
Tracked by hermes-agent.reviews — June 29, 2026