Crash after 8 hrs and 134,615 processes were spawned

[HeYzZe]

How can we reproduce the crash?

Relevant log output

Bun v1.1.17 (bb66bba1) Linux x64 (baseline)
WSL Kernel v5.15.133 | glibc v2.35
Args: "kuzco" "worker" "start"
Features: jsc Bun.stderr Bun.stdin(2) Bun.stdout fetch(11427) spawn(134615) WebSocket(8)
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:process" "node:readline" "node:stream" "node:string_decoder" "node:timers" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "node:diagnostics_channel"
Elapsed: 31070157ms | User: 127310ms | Sys: 89251ms
RSS: 0.02ZB | Peak: 1.19GB | Commit: 0.02ZB | Faults: 0

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.1.17/B_1bb66bbaA+gigoQ21ozmE+xyQqxzrmDk2kwtDk0jtrDknpm/D29rl/Ds13rpDg25s+CksllBA2AA

Stack Trace (bun.report)

Bun v1.1.17 (bb66bba) on linux x86_64baseline []

Segmentation fault at address 0x00000000

• ld-temp.o:0: WTF::jscSignalHandler
• ??
• http.zig:2098: src.http.HTTPClientResult.Callback.New
• http.zig:3146: src.http.NewHTTPContext
• uws.zig:951: src.deps.uws.NewSocketHandler
• context.c:534: us_internal_socket_after_resolve
• loop.c:198: us_loop_run_bun_tick
• uws.zig:1283: src.http.HTTPThread.processEvents
• http.zig:815: Thread.PosixThreadImpl.spawn__anon_82729.Instance.entryFn
• ??

[Jarred-Sumner]

0.02ZB

hmm I wonder why it thinks 0.2 zetabytes were allocated (200,000,000 GB)