oven-sh / bun

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

1.1.27 `bun --bun run docusaurus build --no-minify` segfaults #13584

Closed o-l-a-v closed 1 month ago

o-l-a-v commented 2 months ago

How can we reproduce the crash?

Windows 11 23H2, Bun v1.1.26, PowerShell v7.4.5 -noprofile, Docusaurus 3.5.2.

Reproduce:

Bun crashes and removes content in the terminal, so had to take a screen recording instead. Screenshot of the screen recording:

image

Using the image to text functionality in Windows snipping tool:

Bun v1.1.26 (0a37423b) Windows x64
Windows v.win10_fe
CPU: sse42 avx avx2
Args: "node" "C:\Users\olav.birkeland\Desktop\tesrspress\website\node_modules@docusaurus\core\bin\docusaurus.mjs" "build" " -- no-minify"
Features: jsc Bun. stderr Bun. stdin(2) transpiler_cache(36) tsconfig(175)
Builtins: "bun:jsc" "bun:main" "node: assert" "node: async_hooks" "node: buffer" "node: child_process" "node: constants" "node:crypto" "node:dns" "node: events" "node:fs" "node:fs/promise
et" "node: os" "node : path" "node: perf_hooks" "node : process" "node: querystring" "node : readline" "node: stream" "node : string_decoder" "node: tls" "node:tty" "node:url" "node: util" "node:
reads" "node: punycode" "ws" "node: v8" "node: http2"
Elapsed: 13277ms | User: 6375ms | Sys: 1296ms
RSS: 1.60GB | Peak: 1.61GB | Commit: 19.26GB | Faults: 445756

panic(main thread): Segmentation fault at address 0x13FFFFFFC
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/wn10a37423AugggwC8m7g6C_A2C4/////B

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.26 (0a37423) on windows x86_64 [RunAsNodeCommand]

Segmentation fault at address 0x13FFFFFFC

SunsetTechuila commented 2 months ago

somehow cannot be reproduced on debug builds image

o-l-a-v commented 2 months ago

Tried on a different computer, got a different error.

Bun v1.1.26 (0a37423b) Windows x64
Windows v.win10_fe
CPU: sse42 avx avx2
Args: "node" "C:\Users\olavb\Desktop\JS\website\node_modules@docusaurus\core\bin\docusaurus.mjs" "build" " -- no-minify"
Features: jsc Bun. stderr Bun. stdin(2) transpiler_cache(36) tsconfig(177)
Builtins: "bun: jsc" "bun: main" "node : assert" "node: async_hooks" "node: buffer" "node: child_process" "node: constants" "nod
e: 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: string_decoder"
"node: tls" "node: tty" "node: url" "node: util" "node: util/types" "node: vm" "node: zlib" "node: worker_threads" "node : punycod
e" "ws" "node: v8" "node:http2"
Elapsed: 24664ms | User: 8390ms | Sys: 703ms
RSS: 1.48GB | Peak: 1.48GB | Commit: 19.07GB | Faults: 423031

panic(main thread): Segmentation fault at address 0xE
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/wn10a37423AugggwCm26g6C_A2Ac

Stack trace when going to that last URL:

Bun v1.1.26 (0a37423) on windows x86_64 [RunAsNodeCommand]

Segmentation fault at address 0x0000000E

o-l-a-v commented 1 month ago

Happens with v1.27.0 too.

https://github.com/user-attachments/assets/16a67983-1a73-4cb8-85ef-cbb33c2218e4

o-l-a-v commented 1 month ago

Can't reproduce with Bun v1.1.28.

https://github.com/user-attachments/assets/1eb28b72-17ee-4cc0-8272-ed369946b3ff