claude-code - 💡(How to fix) Fix Claude Code 2.1.122 crashed with embedded Bun v1.3.14 segfault at address 0x38 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54530Fetched 2026-04-30 06:43:06
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

Claude Code crashed with an embedded Bun segfault while editing code in a long-running session.

This appears to be a native runtime crash in the Claude Code/Bun wrapper rather than application code: the terminal printed Bun's crash banner and provided a bun.report URL.

Error Message

Claude Code should not crash the process. If an internal tool/model/runtime error occurs, it should surface as a recoverable CLI error and preserve the active session state.

Root Cause

Claude Code crashed with an embedded Bun segfault while editing code in a long-running session.

This appears to be a native runtime crash in the Claude Code/Bun wrapper rather than application code: the terminal printed Bun's crash banner and provided a bun.report URL.

Code Example

S4 — reject atomic transition + S5 approve rollback event 위치 수정

---

S3 — child terminal lifecycle (parent request_status 갱신)

---

Symbioting… (2m 10s · ↓ 10.0k tokens · thought for 14s)

---

Bun v1.3.14 (0a466a11) macOS Silicon
Args: "claude" "--dangerously-skip-permissions"
Elapsed: 10620675ms | User: 817964ms | Sys: 175876ms
RSS: 0.20GB | Peak: 0.46GB | Commit: 0.02ZB | Faults: 51252 | Machine: 8.59GB

panic(main thread): Segmentation fault at address 0x38
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
RAW_BUFFERClick to expand / collapse

Summary

Claude Code crashed with an embedded Bun segfault while editing code in a long-running session.

This appears to be a native runtime crash in the Claude Code/Bun wrapper rather than application code: the terminal printed Bun's crash banner and provided a bun.report URL.

Crash details

  • Claude Code version in crashed session: 2.1.122
  • Current claude --version after restart: 2.1.123 (Claude Code)
  • Runtime shown in crash banner: Bun v1.3.14 (0a466a11) macOS Silicon
  • OS: macOS arm64
    • sw_vers: ProductVersion 26.2, BuildVersion 25C56
    • crash banner displayed: macOS v26.27
  • Invocation args in crash banner: "claude" "--dangerously-skip-permissions"
  • Claude Code session id: 7c4589b6-814b-409e-a686-167dc4bd1a2c
  • Bun crash report URL:

What was happening

Claude Code was in a long-running coding session, editing Python backend files. The immediate visible task before the crash was:

S4 — reject atomic transition + S5 approve rollback event 위치 수정

Right before that, Claude Code had successfully applied an edit for:

S3 — child terminal lifecycle (parent request_status 갱신)

Then the UI showed:

✽ Symbioting… (2m 10s · ↓ 10.0k tokens · thought for 14s)

After that, the process crashed with the Bun banner below.

Crash excerpt

Bun v1.3.14 (0a466a11) macOS Silicon
Args: "claude" "--dangerously-skip-permissions"
Elapsed: 10620675ms | User: 817964ms | Sys: 175876ms
RSS: 0.20GB | Peak: 0.46GB | Commit: 0.02ZB | Faults: 51252 | Machine: 8.59GB

panic(main thread): Segmentation fault at address 0x38
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Expected behavior

Claude Code should not crash the process. If an internal tool/model/runtime error occurs, it should surface as a recoverable CLI error and preserve the active session state.

Actual behavior

The Claude Code process terminated with a Bun segmentation fault. The terminal became unusable and had to be restarted/resumed manually.

Notes

  • I checked ~/Library/Logs/DiagnosticReports and did not find a matching .ips crash report.
  • The crash happened during agent/editor activity, not while running project tests or executing the edited application code.
  • The session was resumable afterward, but the crash interrupted an in-progress multi-step code edit.

extent analysis

TL;DR

The most likely fix is to update Claude Code to the latest version and avoid using the --dangerously-skip-permissions flag.

Guidance

  • Check the Bun crash report at the provided URL for more detailed information about the crash.
  • Try reproducing the issue without the --dangerously-skip-permissions flag to see if it's related to the crash.
  • Update Claude Code to the latest version, as the current version in the crashed session (2.1.122) is older than the current version (2.1.123).
  • Monitor the issue to see if it persists after updating and removing the flag.

Notes

The crash appears to be related to a native runtime issue in the Bun wrapper, and the provided information is not sufficient to determine the root cause.

Recommendation

Apply workaround: avoid using the --dangerously-skip-permissions flag and update Claude Code to the latest version, as this may resolve the issue or provide more information about the crash.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Claude Code should not crash the process. If an internal tool/model/runtime error occurs, it should surface as a recoverable CLI error and preserve the active session state.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Claude Code 2.1.122 crashed with embedded Bun v1.3.14 segfault at address 0x38 [1 comments, 2 participants]