`claude --continue` crashes with SIGILL (Illegal instruction) — reproducible across v2.1.49 and v2.1.50

Environment

• Claude Code: v2.1.49 and v2.1.50 (standalone binary)
• Bun: v1.3.10 (bundled)
• OS: Fedora 43, Linux 6.18.8-200.fc43.x86_64, glibc 2.42
• CPU: x86_64 with sse42 popcnt avx avx2 avx512
• Terminal: tmux session, fish shell
• RAM: 66.51GB

Description

claude --continue crashes with SIGILL (Signal 4 — Illegal instruction) after extended runtime (~19+ hours). This has happened twice on different versions with identical crash stack traces, suggesting a deterministic bug in the bundled Bun runtime.

Crash details

Both crashes share the same offsets in the Claude binary:

#0  +0x2e49514  (crash handler)
#1  +0x2cc6377
#2  +0x2c0f4a8
#3  +0x466448d
#4  __restore_rt (libc signal handler)
#5  +0x3f12815  ← actual illegal instruction
#6  +0x3f39257  ← repeated 3-5 times (recursion)

The recursive frame at +0x3f39257 appears 3 times in the v2.1.49 crash and 5 times in the v2.1.50 crash. The SIGILL at +0x3f12815 may indicate JIT-emitted code using an unsupported instruction, or memory corruption of JIT code pages.

Occurrence 1 — v2.1.49 (Feb 21)

• PID: 2804997
• Elapsed: unknown
• Coredump: 221.8MB (available locally)

Occurrence 2 — v2.1.50 (Feb 23)

• PID: 3645668
• Elapsed: ~70906 seconds (~19.7 hours)
• RSS display showed "0.02ZB" (likely overflow bug in Bun's crash reporter)
• Coredump: 173.2MB (available locally)

Bun crash report URL

https://bun.report/1.3.10/B_11423d3cmgkgEuhogC4oi5wE+oxGslpuiEslpuiEslpuiEslpuiEslpuiE_____________A24//Bqikm76D

Notes

• Both crashes happened with claude --continue in a tmux session
• Both loaded native .node addons from /tmp/ (since deleted)
• The identical offsets across two versions suggest the Bun binary or this code path didn't change between releases
• Long runtime before crash may indicate a slow memory leak, accumulating JIT state, or timer-related issue