Long bun test --isolate runs crash with SIGILL mid-run

“Symptom: bun test --isolate <corpus> (~650 test files, ~12.4k tests, ~5.4M expect calls) dies with SIGILL / exit code 132 partway through the corpus.”

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/19100/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

Large suites die partway through with exit code 132 and no summary; the same files pass when run in 80-file chunks.

Is this your bug?

File my report

Where: bun test runner
Error text: panic(main thread): Segmentation fault at address 0x4
Versions: 1.3.14
Platforms: Linux
How bad: Breaks a normal workflow.

Not quite your bug?

Original reports2, newest first

Oct 18, 2026bun test --isolate SIGILL (rc132) mid-run on a large TypeScript corpus; chunked decomposition passes clean - bun 1.3.14#45981
Oct 18, 2026Bun 1.3.14 SIGILL rc132 (main-thread segfault at 0x4) on long bun test --isolate runs (~1.7k files); chunked legs always clean#45899