bun has crashed
Closed this issue · 2 comments
How can we reproduce the crash?
Bun v1.2.19 (aad3abe) Windows x64 (baseline)
Windows v.win10_cu
CPU: sse42 avx avx2
Args: "C:\users\srs.local\bin\claude.exe"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch(1774) jsc spawn(220) standalone_executable
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:domain" "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:querystring" "node:stream" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "undici" "ws" "node-fetch" "node:inspector" "node:http2"
Elapsed: 731496ms | User: 71203ms | Sys: 19093ms
RSS: 0.83GB | Peak: 4.84GB | Commit: 5.35GB | Faults: 6523128 | Machine: 68.64GB
panic(main thread): Segmentation fault at address 0x5CEF0AC59A0
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.2.19/e_1aad3abeAz/7v//BsyvrwB4k64Dq9mwhB2n/vhB___A288ChmzuqP
Relevant log output
Stack Trace (bun.report)
Bun v1.2.19 (aad3abe) on windows x86_64_baseline [_]
Segmentation fault at address 0x578E5FD0820
queue.h:81:uv__queue_insert_taillibuv.zig:1377:initprocess.zig:1215:spawnProcesshost_fn.zig:27:function
Features: Bun.stderr, Bun.stdin, Bun.stdout, WebSocket, fetch, jsc, spawn, standalone_executable, standalone_executable
Sentry Issue: BUN-R2S
@samuelseidel-remcom, the latest version of Bun is v1.2.22, but the standalone executable is running Bun v1.2.19. When the CLI using Bun's single-file executable next updates it might be fixed.