claude-code - 💡(How to fix) Fix [Bug] Unbounded thread creation causes out-of-memory condition [1 participants]

[{"error":"Error: rg --files exited 2\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:539:84)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T20:05:30.447Z"}]

TL;DR

The issue can be temporarily mitigated by identifying and killing the problematic process using the provided command, but a more permanent solution requires understanding the root cause of the thread explosion.

Guidance

• Investigate the claude session and its associated processes to determine why it's spawning thousands of threads, potentially leading to an Out-of-Memory (OOM) error.
• Use the provided command as a temporary workaround to kill the problematic processes: for pid in (pgrep -f "bash.*claude"); do kill -9 $pid; done.
• Review the error log to understand the context of the error, specifically the rg --files command that exited with a status code of 2, which might be related to the thread explosion.
• Consider monitoring system resources and process activity to detect similar issues before they cause an OOM error.

Example

No specific code example is provided as the issue seems to be related to a specific command or session (claude) that is not fully described.

Notes

The provided solution is a temporary workaround, and the actual fix will depend on understanding the root cause of the thread explosion. The error log suggests an issue with the rg --files command, but its relation to the claude session and the thread explosion is not clear.

Recommendation

Apply workaround: The provided command to kill the problematic processes can be used as a temporary solution until the root cause is identified and fixed.