Bun dev server crashes with segmentation fault when using @nuxt/image

[iamrgroot]

How can we reproduce the crash?

1. Clone https://github.com/iamrgroot/nuxt-website.git
2. Add this docker-compose.override.yml to run the dev server:

   services:
   bun:
   build:
     target: local
   volumes:
     - ./:/app

3. Run docker compose up --build

I've tried both the linux/amd64 and the linux/arm64 images of the oven/bun:latest image.

JavaScript/TypeScript code that reproduces the crash?

Using @nuxt/image in Nuxt3 with Bun causes segmentation faults when using the dev server. Production builds are working fine. Removing @nuxt/image from the Nuxt modules also works fine.

Relevant log output

[0.66ms] ".env"
bun install v1.1.10 (5102a944)

$ nuxt prepare
[nuxt:tailwindcss] ℹ Using Tailwind CSS from ~/assets/css/tailwind.css
✔ Types generated in .nuxt

+ @nuxtjs/i18n@8.3.1
+ @nuxtjs/tailwindcss@6.12.0
+ nuxt-icon@0.6.10
+ typescript@5.4.5
+ @nuxt/image@1.7.0
+ @radix-icons/vue@1.0.0
+ @vueuse/core@10.9.0
+ class-variance-authority@0.7.0
+ clsx@2.1.1
+ nuxt@3.11.2
+ radix-vue@1.7.4
+ shadcn-nuxt@0.10.4
+ strava@2.3.0
+ tailwind-merge@2.3.0
+ tailwindcss-animate@1.0.7
+ vue@3.4.27
+ vue-router@4.3.2

942 packages installed [52.93s]
$ nuxt dev
Nuxt 3.11.2 with Nitro 2.9.6

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

[nuxt:tailwindcss] ℹ Using Tailwind CSS from ~/assets/css/tailwind.css
  ➜ DevTools: press Shift + Alt + D in the browser (v1.3.1)

[nuxt:tailwindcss] ℹ Tailwind Viewer: http://localhost:3000/_tailwind/
ℹ Vite server warmed up in 785ms
[nitro] ✔ Nuxt Nitro server built in 525 ms
ℹ Vite client warmed up in 1682ms
============================================================
Bun v1.1.10 (5102a944) Linux arm64
Args: "node" "/app/node_modules/.bin/nuxt" "dev"
Features: jsc Bun.stdin(4) Bun.stdout bunfig dotenv(2) http_server spawn tsconfig_paths(14) tsconfig(33)
Builtins: "bun:jsc" "bun:main" "detect-libc" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "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:readline" "node:stream" "node:stream/promises" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:vm" "node:zlib" "node:worker_threads" "ws" "node-fetch" "node:v8"
Elapsed: 4946ms | User: 4254ms | Sys: 570ms
RSS: 0.80GB | Peak: 1.03GB | Commit: 0.80GB | Faults: 32

panic: 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.1.10/Ln15102a94A6qghoG+h2hgE+5D__m7w62Dm/ggxEuz+84Eu9418E+2l+7D_A2A0B

error: script "dev" was terminated by signal SIGTRAP (Trace or breakpoint trap)
Trace/breakpoint trap

Stack Trace (bun.report)

Bun v1.1.10 (5102a94) on linux aarch64 [RunAsNodeCommand]

Segmentation fault at address 0x0000001A

• ld-temp.o:0: WTF::jscSignalHandler
• mod.rs:0: ??
• 2 unknown/js code
• ld-temp.o:0: llint_call_javascript
• ld-temp.o:0: JSC::Interpreter::executeCall
• ld-temp.o:0: JSC::runJSMicrotask
• ld-temp.o:0: JSC::VM::drainMicrotasks
• BunProcess.cpp:2532: Bun::jsFunctionDrainMicrotaskQueue
• 1 unknown/js code

[iamrgroot]

I've noticed Bun does not crash when I delete the .nuxt folder