Segmentation fault (SIGILL) in long-running parallel async processes with high-frequency database operations

[Ch-Hazell]

How can we reproduce the crash?

Bun crashes with segmentation fault after running a parallel benchmark for ~2 hours. The process involves 20 concurrent workers performing high-frequency database operations (ClickHouse inserts every 100ms).

Relevant log output

Bun v1.2.22 (6bafe260) Linux x64
Linux Kernel v6.8.12 | glibc v2.39
CPU: sse42 popcnt avx avx2
Args: "bun" "run" "src/mock/parallelBenchmark.ts" "--workers" "20"
Features: dotenv fetch(93589) jsc tsconfig 
Builtins: "bun:main" "node:buffer" "node:crypto" "node:dns" "node:events" "node:fs" "node:http" "node:https" "node:net" "node:os" "node:path" "node:stream" "node:util" "node:zlib" 
Elapsed: 7548224ms | User: 7415273ms | Sys: 1458506ms
RSS: 0.02ZB | Peak: 0.47GB | Commit: 0.02ZB | Faults: 15 | Machine: 0.54TB

panic: Segmentation fault at address 0x0
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:

 https://bun.report/1.2.22/lr16bafe26QgwkQkj16vE+ypRwy2rsDuwkqnDmqlnB2muqCA2AA

error: script "bench:parallel:20" was terminated by signal SIGILL (Illegal instruction)
error: Failed to run "bun" due to signal SIGILL
Illegal instruction

Stack Trace (bun.report)

Bun v1.2.22 (6bafe26) on linux x86_64 [RunCommand]

Segmentation fault at address 0x00000000

• http.zig:983: http.HTTPThread.processEvents
• HTTPThread.zig:214: Thread.PosixThreadImpl.spawn.Instance.entryFn

Features: tsconfig, dotenv, fetch, jsc

[linear]

ENG-20645 Segmentation fault (SIGILL) in long-running parallel async processes with high-frequency database operations

[github-actions]

Thank you for reporting this crash.

For Bun's internal tracking, this issue is BUN-S8R.