Segmentation fault at address 0x0

[syahrulUlum]

How can we reproduce the crash?

No response

JavaScript/TypeScript code that reproduces the crash?

No response

Relevant log output

Bun v1.1.8 (89d25807) Linux x64 (baseline)
Args: "bun", "src/index.ts"
Features: jsc fetch tsconfig(10) 
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:crypto" "node:events" "node:fs" "node:http" "node:https" "node:net" "node:path" "node:querystring" "node:stream" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:punycode" 
Elapsed: 438ms | User: 365ms | Sys: 71ms
RSS: 1.05GB | Peak: 120.25MB | Commit: 1.05GB | Faults: 3

panic(main thread): Segmentation fault at address 0x0
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Stack Trace (bun.report)

Bun v1.1.8 (89d2580) on linux x86_64_baseline [AutoCommand]

Segmentation fault at address 0x00000000

• ld-temp.o:0: void WTF::URLParser::parse<char16_t>
• ??
• bit_set.zig:650: src.js_printer.NewPrinter
• js_printer.zig:1143: src.js_printer.NewPrinter
• 1 unknown/js code
• ld-temp.o:0: llint_function_for_call_arity_check
• ld-temp.o:0: llint_function_for_call_arity_check
• ld-temp.o:0: llint_op_eq_null_wide32
• ld-temp.o:0: llint_op_eq_null_wide32
• ld-temp.o:0: llint_op_eq_null_wide32