2 people reported
All time, since Aug 9.
SIGSEGV in JSC GC and Workers
“Both new crashes are pointer corruption: the collector and a Worker each dereference a small integer as an address.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/5529/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
SIGSEGV in JSC garbage collector and Worker threads in long-running processes. Crashes land in a "Heap Helper Thread" or "Worker" on macOS arm64, dereferencing small NULL-based addresses after hours of Worker churn.
Is this your bug?
File my report- Where
- Workers
- Error text
signal: SIGSEGV KERN_INVALID_ADDRESS at 0x0000000000000005- Versions
- 1.4.0-canary.1 to 1.4.3-canary.1
- Platforms
- macOS
- How bad
- Stops work: a core feature can't be used.
Not quite your bug?
- Test workers segfault2 people
- Panic on thread EAGAIN2 people
- Long bun test --isolate runs crash with SIGILL mid-run1 person
Original reports3, newest first
- SIGSEGV at NULL+0xd0 / NULL+0x38 in a JSC Heap Helper / Worker thread after hours of Worker churn in a standalone executable (1.4.2, macOS arm64) - three reports, same frames#43663
- JSC heap corruption still reproduces on 1.4.3-canary: SIGSEGV in the parallel marker and in a Worker (follow-up to #37284)#41857
- SIGSEGV inside JSC GC on 1.4.0-canary (macOS arm64): parallel marker crashes in JSCellButterfly::visitChildren; Worker crashes in JSRopeString finishSweep under Bun.gc(true)#37284