(bun + nitro + i18next) crash

[medz]

How can we reproduce the crash?

I don't know why, I integrated i18next in Nitro and that's it

Use the Nitro plugin, load i18next, and run it in dev mode. Then edit any code related to i18next in the editor. It crashes after a few edits.

Relevant log output

seven@Sevens-MacBook-Pro api-server % bun run dev
$ bun --bun nitro dev

  ➜ Local:    http://localhost:3000/
  ➜ Network:  use --host to expose

✔ Nitro Server built in 342 ms                                                  nitro 11:34:20 PM
✔ Nitro Server built in 164 ms                                                  nitro 11:34:23 PM
✔ Nitro Server built in 157 ms                                                  nitro 11:34:25 PM
============================================================
Bun v1.2.4 (fd9a5ea6) macOS Silicon
macOS v15.3.1
Args: "node" "/Users/seven/workspace/panews-api-server/node_modules/.bin/nitro" "dev"
Features: Bun.stderr(7) Bun.stdin(6) Bun.stdout(6) http_server(3) jsc spawn transpiler_cache(46) tsconfig(5) tsconfig_paths workers_spawned(3) workers_terminated(2) process_dlopen(4)
Builtins: "bun:jsc" "bun:main" "detect-libc" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:process" "node:querystring" "node:stream" "node:stream/promises" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:vm" "node:zlib" "node:worker_threads" "node-fetch" "node:v8"
Elapsed: 5674ms | User: 2187ms | Sys: 333ms
RSS: 0.51GB | Peak: 0.51GB | Commit: 0.91GB | Faults: 98

panic: Bus error at address 0x15B521B90
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.4/Mn1fd9a5eauLugg0gQ_+s685B+hz65Bmtl45B+3zn5B+nm5nCmwmkkBm6z7a+537a+wyliBA4Cg5toq7C

error: Failed to run "nitro" due to signal SIGTRAP
error: script "dev" was terminated by signal SIGTRAP (Trace or breakpoint trap)
zsh: trace trap  bun run dev

Stack Trace (bun.report)

Bun v1.2.4 (fd9a5ea) on macos aarch64 [AutoCommand]

Bus error at address 0x15EA27FA0

• 1 unknown/js code
• JSC::WeakBlock::lastChanceToFinalize
• JSC::PreciseAllocation::lastChanceToFinalize
• JSC::MarkedSpace::lastChanceToFinalize
• JSC::Heap::lastChanceToFinalize
• JSC::VM::~VM
• WebWorker__dispatchExit
• bun.js.web_worker.WebWorker.exitAndDeinit
• bun.js.javascript.OpaqueWrap__anon_1314444__struct_1314578.callback
• JSC__VM__holdAPILock

Features: transpiler_cache, tsconfig, workers_spawned, workers_terminated, process_dlopen, Bun.stderr, fetch, http_server, jsc

_{Sentry Issue: BUN-DD0}

[medz]

I made a minimal crash demo 👉 https://github.com/medz/bun-nitro-i18next-crash

[medz]

I made a minimal crash demo 👉 https://github.com/medz/bun-nitro-i18next-crash

Note: After starting dev, visit the route a few times and then come back to edit the file, which is more likely to trigger a crash.

[medz]

Updates：

Clarification from the i18next author: i18next/i18next#2290 (comment)

This is not an i18next issue.

But the combination of this issue is weird, I used to have Bun + Nitro + Prisma without any crashes. But now it happens in dev.