You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I triggered this bug by running a @verdant-web/server instance and then attempting to sync some data into it. Since the crash specifically occurs when the database is opened, you can probably reproduce it just by trying to use better-sqlite3.
Relevant log output
107 |return opts[p] || p;
108 | })
109 | );
110 | tries.push(n);
111 | try {
112 | b = opts.path ? requireFunc.resolve(n) : requireFunc(n);
^
error: LoadLibrary failed: A dynamic link library (DLL) initialization routine failed.
code: "ERR_DLOPEN_FAILED"
at bindings (C:\Users\ibiyemi\projects\archivist\sync\node_modules\bindings\bindings.js:112:48)
at new Database (C:\Users\ibiyemi\projects\archivist\sync\node_modules\better-sqlite3\lib\database.js:48:29)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\database.js:12:24)
at openDatabase (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\database.js:6:36)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\Databases.js:23:48)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\Databases.js:13:27)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\SqlReplicas.js:14:39)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\storage\sqlShard\SqlReplicas.js:12:27)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\ServerLibrary.js:12:57)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\ServerLibrary.js:11:45)
at <anonymous> (C:\Users\ibiyemi\projects\archivist\sync\node_modules\@verdant-web\server\dist\esm\ServerLibrary.js:27:40)
Bun v1.2.8 (Windows x64)
============================================================
Bun v1.2.8 (adab0f64) Windows x64
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\ibiyemi\.bun\bin\bun.exe""run""index.ts"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) dotenv(2) http_server jsc tsconfig(17) process_dlopen
Builtins: "bun:main""node:async_hooks""node:buffer""node:crypto""node:events""node:fs""node:fs/promises""node:http""node:net""node:os""node:path""node:process""node:querystring""node:stream""node:tty""node:url""node:util""node:zlib""ws"
Elapsed: 4538ms | User: 328ms | Sys: 250ms
RSS: 0.28GB | Peak: 0.28GB | Commit: 0.39GB | Faults: 70233
panic(main thread): Segmentation fault at address 0x7FFA7D88A4B0
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.8/wr1adab0f6kIuwgU_CSntdll.dll+r8ICSntdll.dll64xsBCSntdll.dllorrsBCYKERNEL32.DLL2qsQq7Sk16jGg658F2zu3mBq0k6EA20//Bgryix9Derror: script "start" exited with code 1
Stack Trace (bun.report)
Bun v1.2.8 (adab0f6) on windows x86_64 [RunCommand]
How can we reproduce the crash?
I triggered this bug by running a
@verdant-web/server
instance and then attempting to sync some data into it. Since the crash specifically occurs when the database is opened, you can probably reproduce it just by trying to usebetter-sqlite3
.Relevant log output
Stack Trace (bun.report)
Bun v1.2.8 (
adab0f6
) on windows x86_64 [RunCommand]Segmentation fault at address 0x7FFA7DACA4B0
0x238bf
in ntdll.dll0xb238d
in ntdll.dll0xb16b4
in ntdll.dll0x418ab
in KERNEL32.DLLGlobal.zig:124
:exit
javascript.zig:1441
:globalExit
bun_js.zig:341
:start
bindings.cpp:5184
:JSC__VM__holdAPILock
VM.zig:36
:holdAPILock
Features: tsconfig, process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, dotenv, http_server, jsc
Sentry Issue: BUN-EWK
The text was updated successfully, but these errors were encountered: