Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bun Segmentation fault at address 0x0 oh no: Bun has crashed. This indicates a bug in Bun, not your code. #15680

Open
previraza opened this issue Dec 10, 2024 · 2 comments
Labels
crash An issue that could cause a crash linux An issue that occurs on Linux

Comments

@previraza
Copy link

previraza commented Dec 10, 2024

How can we reproduce the crash?

bun --bun dev -p 8081

Relevant log output

$ next dev --turbopack -p "8081"
   ▲ Next.js 15.0.3 (Turbopack)
   - Local:        http://localhost:8081
   - Environments: .env

 ✓ Starting...
 ✓ Compiled in 368ms
 ✓ Ready in 1540ms
============================================================
Bun v1.1.38 (bf2f153f) Linux x64
Linux Kernel v6.8.0 | glibc v2.39
CPU: sse42 popcnt avx avx2
Args: "/home/mci/.bun/bin/bun" "/home/mci/xTest/snen/node_modules/next/dist/server/lib/start-server.js"
Features: Bun.stdin dotenv fetch(2) http_server jsc spawn transpiler_cache(21) tsconfig tsconfig_paths process_dlopen 
Builtins: "bun:jsc" "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns/promises" "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/web" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:vm" "node:zlib" "node:worker_threads" "ws" "node:v8" "node:diagnostics_channel" 
Elapsed: 3773ms | User: 2593ms | Sys: 259ms
RSS: 1.07GB | Peak: 0.33GB | Commit: 1.07GB | Faults: 0

panic(main thread): Segmentation fault at address 0x0
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.38/la1bf2f153gB9v76/duw1/kE+xpRk/l3iE8thxmD09qpjE_8mgh7D8mgh7D8mgh7D_A2AA

Stack Trace (bun.report)

Bun v1.1.38 (bf2f153) on linux x86_64 [AutoCommand]

Segmentation fault at address 0x00000000

Features: process_dlopen, Bun.stdin, dotenv, fetch, http_server, jsc, spawn, transpiler_cache, tsconfig, tsconfig_paths, tsconfig_paths

@previraza previraza added the crash An issue that could cause a crash label Dec 10, 2024
@github-actions github-actions bot added the linux An issue that occurs on Linux label Dec 10, 2024
Copy link
Contributor

Thank you for reporting this crash.

For Bun's internal tracking, this issue is BUN-9K9.

@Jarred-Sumner
Copy link
Collaborator

Please let us know if you still run into this again on Bun v1.1.42+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crash An issue that could cause a crash linux An issue that occurs on Linux
Projects
None yet
Development

No branches or pull requests

2 participants