[BUG] Multi-window crash: raw data floods terminals, all agent sessions dead simultaneously (v2.1.90, Windows)
Summary
With 10+ Claude Code windows running simultaneously on Windows, all windows crashed at once. Multiple terminals were flooded with massive amounts of raw comma-separated numbers — not application output, appears to be buffer contents or Bun crash dump data being written to stdout uncontrollably.
Screenshot
User preserved a screenshot showing the full desktop: 10+ Claude Code terminal windows, multiple showing raw number dumps flooding the terminal output area. All agent sessions were dead simultaneously.
What was running
- RAM Audit Agent
- Agent B Exit Forensics
- Agent C Live Features
- Agent D V3 Retrain
- Agent A Entry Forensics
- Agent F 1-Min Pipeline
- git manager
- Bug Manager
- IQ Feed connectivity monitor
- Multiple PowerShell windows
All running active work — pipeline builds, file reads, model training.
Impact
Total system failure. All agent sessions dead simultaneously. The bug-reporter agent was also dead, so the user could not even file a report during the incident. All overnight pipeline work lost. Had to restart everything from scratch.
Environment
- v2.1.90, Windows 11
- Windows Terminal / PowerShell
- 10+ simultaneous Claude Code windows
- Active pipeline work (file I/O, Python builds, model training)
- Max plan, Opus 4.6
Likely root cause
Bun runtime memory exhaustion or GC crash under multi-process load. Each Claude Code window is an independent node/Bun process. 10+ windows x ~800MB each = 8+ GB just for Claude Code, on top of active Python pipeline processes consuming 12+ GB.
Related issues
- #1421 — JS Heap OOM from multiple windows
- #36132 — Bun mimalloc leaks ~1GB/hour, crashes after 12-24h
- #21469 — Random Bun segfaults on Windows
- #41831 — Tool calls stall 10-20 min + Bun GC crash
- #42535 — Many MCP servers break subagents (Explore tools)
The raw number dump to stdout is distinctive — this is not a normal crash or hang. Something in the Bun runtime or terminal rendering layer is dumping raw buffer contents when it fails.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗