-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bun has crashed #11907
Comments
Is there anything more you can share with us? The stacktrace says it crashed in a One thing that's a little interesting is that number |
These are excerpts, hope it helps you.
|
Oh, I wonder if it's |
Ok, thanks. |
replace |
How can we reproduce the crash?
This is not a server resource issue.
This is a fairly powerful Amazon cloud server that runs only bun,
serves about 200 WebSoscket connections...
Relevant log output
Stack Trace (bun.report)
Bun v1.1.13 (
bd6a605
) on linux x86_64 [AutoCommand]Segmentation fault at address 0x00000002
ld-temp.o:0
:WTF::jscSignalHandler
??
ld-temp.o:0
:llint_call_javascript
ld-temp.o:0
:JSC::Interpreter::executeCall
ld-temp.o:0
:JSC::profiledCall
bindings.cpp:2285
:JSObjectCallAsFunctionReturnValue
server.zig:0
:src.deps.uws.AnyWebSocket.cork__anon_347613.Wrapper.wrap
MoveOnlyFunction.h:247
:uws_ws_cork
uws.zig:0
:src.deps.uws.WebSocketBehavior.Wrap
MoveOnlyFunction.h:247
:uWS::WebSocketContext<false, true, void*>::handleFragment
The text was updated successfully, but these errors were encountered: