Bun crashed when executing `serve` with bun `bunx --bun serve` on VMs

[mavyfaby]

How can we reproduce the crash?

Executing PORT=7000 bunx --bun serve .output/public crashed bun. Work's with node tho.

Relevant log output

root@srv548714:~/@nextgen/frontend# PORT=7000 bunx --bun serve .output/public
 ERROR  Cannot copy server address to clipboard: Both xsel and fallback failed.

   ┌────────────────────────────────────────────┐
   │                                            │
   │   Serving!                                 │
   │                                            │
   │   - Local:    http://localhost:7000        │
   │   - Network:  http://XXX.XXX.XXX.XX:7000   │
   │                                            │
   └────────────────────────────────────────────┘

============================================================
Bun v1.1.26 (0a37423b) Linux x64
Linux Kernel v6.8.0 | glibc v2.39
CPU: sse42 popcnt avx avx2 avx512
Args: "node" "/root/.nvm/versions/node/v22.5.0/bin/serve" ".output/public"
Features: jsc Bun.stdin(2) http_server spawn transpiler_cache tsconfig_paths(2) tsconfig(2)
Builtins: "bun:main" "node:assert" "node:buffer" "node:child_process" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:net" "node:os" "node:path" "node:process" "node:querystring" "node:stream" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:punycode"
Elapsed: 197ms | User: 190ms | Sys: 59ms
RSS: 1.07GB | Peak: 88.22MB | Commit: 1.07GB | Faults: 0

panic(main thread): Segmentation fault at address 0x20
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.26/ln10a37423Aqggh0Du+u1kE+xpRmqju/Css+v4Dw0hp4Euvv+1E63271Eonw91E6m271E46/h2EA2AgC

Illegal instruction (core dumped)

Stack Trace (bun.report)

It's weird, bun report link shows:

{"error":"Could not find debug info for this version of Bun."}

[mavyfaby]

It seems to be fixed on the latest release. I'll now close the issue.

[mavyfaby]

Nah, doesn't work on VMs