Server crashed with segmentation fault

[Torsten85]

How can we reproduce the crash?

Our server just crashed twice with the attached cryptic error. I'm not sure if this is of any value, but the Bun output told me to file an issue 😉

Relevant log output

Stack Trace (bun.report)

Bun v1.1.34 (5e5e7c6) on linux aarch64 [AutoCommand]

Segmentation fault at address 0x00000050

• HttpContext.h:130: uWS::HttpContext<false>::init(...)::__invoke
• HttpContext.h:130: uWS::HttpContext<false>::init(...)::__invoke
• socket.c:218: us_socket_close
• loop.c:433: us_loop_run_bun_tick
• event_loop.zig:0: src.bun.js.event_loop.EventLoop.autoTickActive
• bun_js.zig:409: src.bun.js.javascript.OpaqueWrap__anon_55177__struct_96246.callback
• bindings.cpp:4854: JSC__VM__holdAPILock
• shimmer.zig:197: src.bun_js.Run.boot

Features: workers_spawned, Bun.stdin, abort_signal, fetch, http_server, jsc

[github-actions[bot]]

@Torsten85, thank you for reporting this crash. The latest version of Bun is v1.1.36, but this crash was reported on Bun v1.1.34.

Are you able to reproduce this crash on the latest version of Bun?

bun upgrade

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

[Jarred-Sumner]

It’s a little bit helpful but is there any code you could share with us?