[BUG] /status slash command freezes terminal UI on macOS — requires process kill to recover

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/32739
2. https://github.com/anthropics/claude-code/issues/33700
3. https://github.com/anthropics/claude-code/issues/32728

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Additional Evidence: V8 OOM Crash Report (March 6)

Found a related Node.js crash report in ~/Library/Logs/DiagnosticReports/node-2026-03-06-115650.ips from the same machine. While today's /status freeze was a PTY deadlock (process stayed alive but unresponsive), this earlier crash shows Claude Code's Node.js process hitting V8 heap exhaustion.

Crash Summary

• Date: 2026-03-06 11:56:50 +0800
• Process: node (PID 17039), spawned from Ghostty terminal
• Duration before crash: ~19 seconds
• Exception: EXC_CRASH / SIGABRT (Abort trap: 6)
• Root cause: abort() called by node::OOMErrorHandler after v8::internal::Heap::FatalProcessOutOfMemory

Crash Stack (Thread 0)

__pthread_kill
pthread_kill
abort
node::OOMErrorHandler(char const*, v8::OOMDetails const&)
v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, ...)
v8::internal::Heap::FatalProcessOutOfMemory(char const*)
v8::internal::Heap::CollectGarbage(...)
v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(...)
v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(...)
v8::internal::Factory::NewJSObjectFromMap(...)
v8::internal::Runtime_CreateObjectLiteral(...)

Two Distinct Failure Modes

| Date | Failure | Mechanism | Recovery |
|------|---------|-----------|----------|
| March 6 | Node.js crash | V8 heap OOM -> SIGABRT | Auto (process died) |
| March 13 | Terminal freeze (/status) | Stalled event loop -> PTY deadlock | Manual (tmux respawn-pane -k) |

Both occurred with multiple MCP servers connected (4 custom MCP servers). The OOM crash suggests memory pressure from MCP server child processes may be a contributing factor.

Environment

• macOS Darwin 25.3.0 (Apple Silicon, Mac16,13)
• Node.js at /usr/local/bin/node
• Claude Code 2.1.74

Closing as duplicate of #32728 (canonical). Added V8 OOM crash evidence and reproduction details there.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.