-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Closed as duplicate of#24028
Labels
Description
How can we reproduce the crash?
I wish I knew using OpenCode randomly crashes bun, I noticed this only recently while developing inside a devcontainer
Relevant log output
Bun v1.3.1 (89fa0f34) Linux arm64
Linux Kernel v6.10.14 | glibc v2.39
CPU: neon fp aes crc32 atomics
Args: "opencode" "--user-agent=opencode/1.0.15" "--env-file=\"\"" "--"
Features: Bun.stderr(4) Bun.stdin(4) Bun.stdout(4) abort_signal dotenv(3) fetch(186) http_server jsc shell(57444) spawn(28822) standalone_executable transpiler_cache(4) workers_spawned(2) workers_terminated
Builtins: "bun:ffi" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:console" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:process" "node:readline" "node:stream" "node:string_decoder" "node:timers" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:worker_threads" "undici"
Elapsed: 1707979ms | User: 1029779ms | Sys: 339041ms
RSS: 0.02ZB | Peak: 5.02GB | Commit: 0.02ZB | Faults: 3003413 | Machine: 8.22GB
panic(main thread): Segmentation fault at address 0xFFFF6657E280
oh no: Bun has crashed. This indicates a bug in Bun, not your code.Stack Trace (bun.report)
Bun v1.3.1 (89fa0f3) on linux aarch64 [RunAsNodeCommand]
Segmentation fault at address 0x00000008
crash_handler.zig:331:crash_handler.crashHandler
Features: tsconfig, tsconfig_paths, Bun.stderr, dotenv, jsc
Sentry Issue: BUN-YNV