Open cronJ opened 3 months ago
Bump, I got the same issue with bun --watch ...
============================================================
Bun v1.1.8 (89d25807) Windows x64
Args: "C:\Users\xxxx\.bun\bin\bun.exe", "--watch", "src/app.ts"
Features: jsc Bun.stdin(2) Bun.stdout dotenv fetch transpiler_cache(6) tsconfig_paths(2) tsconfig(5) WebSocket
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:os" "node:path" "node:process" "node:stream" "node:string_decoder" "node:timers" "node:timers/promises" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "undici" "ws"
Elapsed: 1539ms | User: 296ms | Sys: 93ms
RSS: 0.28GB | Peak: 0.28GB | Commit: 0.34GB | Faults: 68455
panic(main thread): Segmentation fault at address 0xFFFFFFFFFFFFFFFF
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
How can we reproduce the crash?
Build the example project from https://bun.sh/guides/ecosystem/discordjs
JavaScript/TypeScript code that reproduces the crash?
Relevant log output
Stack Trace (bun.report)
Bun v1.1.7 (
b0b7db5
) on windows x86_64 [RunCommand]Segmentation fault at address 0xFFFFFFFFFFFFFFFF
??
??
uv__process_poll_req
??
uv_run
uws.zig:2619
:run
JSC__VM__holdAPILock
shimmer.zig:186
:cppFn
run_command.zig:1402
:exec
cli.zig:1733
:start