search

oven-sh / bun

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
https://bun.sh
Other
73.61k stars 2.72k forks source link

Segmentation fault at address 0xD0000003B #13235

Closed AktharAzif closed 1 month ago

AktharAzif commented 1 month ago

How can we reproduce the crash?

No response

Relevant log output

============================================================

Bun Canary v1.1.23-canary.17 (7aaf9357) Linux x64 (baseline)

Linux Kernel v6.1.0 | glibc v2.31

CPU: sse42 popcnt avx avx2 avx512

Args: "bun" "src/index.ts"

Features: jsc abort_signal(255) fetch(10609) http_server tsconfig(13) 

Builtins: "bun:main" "node:assert" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:querystring" "node:stream" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "ws" "node-fetch" "node:http2" 

Elapsed: 10227938ms | User: 956593ms | Sys: 245954ms

RSS: 24.80MB | Peak: 0.41GB | Commit: 24.80MB | Faults: 498

panic(main thread): Segmentation fault at address 0xD0000003B

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.23/Ba27aaf935AihihgCu+5gjE+1mOwhr3jDsh417Dw24m/Esv8u2E8uxu2Ekmvu2Ewnj27Dgq0/9CA2a2D

error: script "start" was terminated by signal SIGILL (Illegal instruction)

Stack Trace (bun.report)

Bun v1.1.23-canary (7aaf935) on linux x86_64_baseline [AutoCommand]

Segmentation fault at address 0xD0000003B

Features: jsc, abort_signal, fetch, http_server, tsconfig

Jarred-Sumner commented 1 month ago

@cirospaciari can you take a look?

Jarred-Sumner commented 1 month ago

We don't have a way to reproduce the issue, but likely this fixes it: https://github.com/oven-sh/bun/pull/13249

Please leave a comment if you still run into the issue after running bun upgrade --canary again and we will continue to investigate.

It would be really helpful if you could provide a way for us to reproduce the issue

AktharAzif commented 1 month ago

@Jarred-Sumner I cannot reproduce this issue as I don't know its exact cause. It happens randomly. I'm using a canary Docker image, so I'll wait for the new release and see if it resolves the problem. Thanks for your help.