Bun crashed with panic

[matinzd]

How can we reproduce the crash?

The code was up on production and I have no idea why. I will try to provide a repro.

JavaScript/TypeScript code that reproduces the crash?

TODO

Relevant log output

mealplan-pdf-generator-mealplan-pdf-1  | ============================================================
mealplan-pdf-generator-mealplan-pdf-1  | Bun v1.1.7 (b0b7db5c) Linux x64 (baseline)
mealplan-pdf-generator-mealplan-pdf-1  | Args: "bun", "server.js"
mealplan-pdf-generator-mealplan-pdf-1  | Features: jsc abort_signal(6) fetch(15383) http_server tsconfig(4) 
mealplan-pdf-generator-mealplan-pdf-1  | Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:crypto" "node:events" "node:fs" "node:http" "node:https" "node:net" "node:os" "node:path" "node:querystring" "node:stream" "node:string_decoder" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node-fetch" 
mealplan-pdf-generator-mealplan-pdf-1  | Elapsed: 776430019ms | User: 1011823ms | Sys: 169556ms
mealplan-pdf-generator-mealplan-pdf-1  | RSS: 0.02ZB | Peak: 2.25GB | Commit: 0.02ZB | Faults: 384
mealplan-pdf-generator-mealplan-pdf-1  | 
mealplan-pdf-generator-mealplan-pdf-1  | panic(main thread): Segmentation fault at address 0x1A
mealplan-pdf-generator-mealplan-pdf-1  | oh no: Bun has crashed. This indicates a bug in Bun, not your code.
mealplan-pdf-generator-mealplan-pdf-1  | 
mealplan-pdf-generator-mealplan-pdf-1  | To send a redacted crash report to Bun's team,
mealplan-pdf-generator-mealplan-pdf-1  | please file a GitHub issue using the link below:
mealplan-pdf-generator-mealplan-pdf-1  | 
mealplan-pdf-generator-mealplan-pdf-1  |  https://bun.report/1.1.7/Ba1b0b7db5AihihgE+2ro+DA2A0B

Stack Trace (bun.report)

Bun v1.1.7 (b0b7db5) on linux x86_64_baseline [AutoCommand]

Segmentation fault at address 0x00000118

• ld-temp.o:0: std::optional<WTF::Vector<unsigned char, 2048ul, WTF::CrashOnOverflow, 16ul, WTF::FastMalloc> > WTF::URLParser::domainToASCII<char16_t>

Features: jsc, tsconfig

[Jarred-Sumner]

Sorry about this.

Would you be able to run bun upgrade and then re-submit the crash report? This stack trace unfortunately doesn't give us much information to go on, but we fixed an issue causing the stacktrace to not have enough information in Bun v1.1.8

[matinzd]

I rebuilt the image using the latest tag and restarted the service. Let's see if it pops up again! Will keep you posted.