Open
Description
How can we reproduce the crash?
It happened when I ran drizzle generate
bunx --bun drizzle-kit generate
The crash happened AFTER the SQL files were generated, which I assume means that the problem is in Bun gracefully exiting.
Relevant log output
============================================================
Bun v1.2.2 (c1708ea6) Linux x64
Linux Kernel v6.12.10 | glibc v2.40
CPU: sse42 popcnt avx avx2
Args: "node" "/home/<redacted>/node_modules/.bin/drizzle-kit" "generate"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) dotenv jsc transpiler_cache(2) tsconfig
Builtins: "bun:main" "node:assert" "node:buffer" "node:child_process" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:module" "node:os" "node:path" "node:process" "node:readline" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:worker_threads"
Elapsed: 21446ms | User: 277ms | Sys: 52ms
RSS: 1.07GB | Peak: 129.79MB | Commit: 1.07GB | Faults: 9
panic(main thread): Segmentation fault at address 0x1A
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.2/ln1c1708eaAzv/7//Bomg8oE+8oPgm//9Dgm//9Dgm//9Dgm//9Dgm//9Dgm//9Dgm//9D_A2A0B
Illegal instruction (core dumped)
Stack Trace (bun.report)
Bun v1.2.2 (c1708ea
) on linux x86_64 [RunCommand]
Segmentation fault at address 0x0000001A
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
Features: Bun.stderr, Bun.stdin, Bun.stdout, dotenv, fetch, jsc, transpiler_cache, tsconfig, tsconfig
Sentry Issue: BUN-4KP
Activity