Why this randomly happen?

[ImBIOS]

How can we reproduce the crash?

I don't know, it's random.

Relevant log output

============================================================
Bun v1.1.30 (7996d06b) Linux x64
Linux Kernel v6.8.0 | glibc v2.39
CPU: sse42 popcnt avx avx2 avx512
Args: "bun" "index.ts" "-b" "false" "-l" "trace" "--serial"
Features: Bun.stdin(2) WebSocket(33) bunfig dotenv(1031) fetch(314) http_server jsc spawn(1421) transpiler_cache(39) tsconfig(17) tsconfig_paths workers_spawned(1030) workers_terminated(1011)
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/win32" "node:perf_hooks" "node:process" "node:readline" "node:stream" "node:stream/promises" "node:string_decoder" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:vm" "node:zlib" "node:worker_threads" "node:punycode" "ws" "node-fetch"
Elapsed: 2047268ms | User: 319580ms | Sys: 94300ms
RSS: 0.02ZB | Peak: 3.33GB | Commit: 0.02ZB | Faults: 193

panic(main thread): 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:

 (redacted)

./some-redacted-bash-file.sh: line 13: 72280 Illegal instruction     (core dumped) bun index.ts -b false -l trace --serial

Stack Trace (bun.report)

Bun v1.1.30 (7996d06) on linux x86_64 [AutoCommand]

Segmentation fault at address 0x00000000

• napi.cpp:447: NAPIFunction::call

Features: workers_spawned, workers_terminated, Bun.stdin, WebSocket, bunfig, dotenv, fetch, http_server, jsc, spawn, transpiler_cache, tsconfig, tsconfig_paths, tsconfig_paths

[Jarred-Sumner]

Tracking this in #15964