Open Abhinav5383 opened 1 month ago
@Abhinav5383, the latest version of Bun is v1.1.30, but this crash was reported on Bun v1.1.20.
Are you able to reproduce this crash on the latest version of Bun?
bun upgrade
Nope, couldn't reproduce either on the version I was or on the latest version
How can we reproduce the crash?
I don't have a good idea how it happened, but it probably happened due to the device losing internet just after bun made a fetch request.
Relevant log output
Bun v1.1.20 (ae194892) Linux x64 Linux Kernel v6.11.2 | glibc v2.40 CPU: sse42 popcnt avx avx2 avx512 Args: "bun" "run" "--hot" "src/index.ts" Features: jsc Bun.stdin abort_signal(2) dotenv fetch(315) http_server spawn transpiler_cache(27) tsconfig_paths(2) tsconfig(3) Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:net" "node:os" "node:path" "node:stream" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" Elapsed: 7223346ms | User: 17890ms | Sys: 1815ms RSS: 9.22GB | Peak: 0.35GB | Commit: 9.22GB | Faults: 401
panic: Segmentation fault at address 0x0 oh no: Bun has crashed. This indicates a bug in Bun, not your code.
error: script "dev" was terminated by signal SIGILL (Illegal instruction) [1] 3200 illegal hardware instruction (core dumped) bun dev
Stack Trace (bun.report)
Bun v1.1.20 (
ae19489
) on linux x86_64 [RunCommand]Segmentation fault at address 0x00000000
ld-temp.o:0
:WTF::Unicode::convertReplacingInvalidSequences
??
http.zig:850
:src.http.start___anon_126724
interpreter.zig:7330
:src.shell.interpreter.Interpreter.Builtin.Cd.handleChangeCwdErr
http.zig:2999
:src.deps.uws.NewSocketHandler
context.c:134
:us_socket_context_adopt_socket
bsd.c:159
:us_loop_run_bun_tick
array_hash_map.zig:2022
:src.http.HTTPThread.processEvents
string_immutable.zig:885
:src.http.NewHTTPContext