Crash: HTTP Client thread SIGABRT (abort() called) in v2.0.69
Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Dec 9, 2025 · closed Dec 15, 2025
Bug Description
This thing is crashing all day
Environment Info
- Platform: darwin
- Terminal: tmux
- Version: 2.0.61
- Feedback ID: 9337e90b-f9ed-461e-9a24-064b5b69e045
EDIT: See Console.app assessment summary and raw logs below (summary generated by CC)
4 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
It's not a "freeze" like the proposed duplicates. It's literally a crash.
[1] 20161 abort claude
⏺ Claude Code 2.0.69 Crash - HTTP Client Thread SIGABRT
Environment
Crash Details
Analysis
The crash originated in the HTTP Client thread with an explicit abort() call, suggesting an assertion failure or panic in Bun's HTTP networking layer. The stack trace shows the crash path went through Bun's internal HTTP handling before triggering the abort.
<details>
<summary>Full crash report</summary>
</details>
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.