Segmentation fault at address 0x00000011

[takiguru]

How can we reproduce the crash?

No response

JavaScript/TypeScript code that reproduces the crash?

No response

Relevant log output

Bun v1.1.7 (b0b7db5c) Linux x64
Args: "bun", "index.ts"
Features: jsc Bun.stdin(2) dotenv(10) fetch(8712) http_server transpiler_cache(32) tsconfig(17) WebSocket(15) 
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:querystring" "node:stream" "node:string_decoder" "node:timers" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "ws" "node-fetch" 
Elapsed: 2194787ms | User: 103974ms | Sys: 24629ms
RSS: 0.72GB | Peak: 0.37GB | Commit: 0.72GB | Faults: 0

panic: Segmentation fault at address 0x6EB8
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.7/la1b0b7db5AqoihgV+0kw+DA2Awr3B

[1]    138709 illegal hardware instruction (core dumped)  bun index.ts

Stack Trace (bun.report)

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

Segmentation fault at address 0x00000011

• ld-temp.o:0: WTF::jscSignalHandler

Features: jsc, fetch, tsconfig

[Jarred-Sumner]

Unfortunately, the crash reporter was not working properly on Linux in Bun v1.1.7 and did not produce a useful stacktrace for us.

This was fixed in Bun v1.1.8. Can you report this again in Bun v1.1.8?