Segmentation fault when connecting to cassandra-driver

[Darker-Ink]

How can we reproduce the crash?

Using this simple code:

import { Client } from "@kastelapp/cassandra-driver"; // custom fork of the library, does not change anything meaningful

const client = new Client({
    keyspace: "keyspace",
    contactPoints: ["localhost"],
    credentials: {
        username: "",
        password: ""
    },
    localDataCenter: "datacenter1"
})

try {
    await client.connect();
    console.log("Connected to Cassandra");
} catch (error) {
    console.error("Failed to connect to Cassandra", error);
}

before it can even connect it Segmentation fault's

Relevant log output

➜  Backend git:(ink/messages) ✗ bun run src/fixtest.ts
============================================================
Bun v1.1.13 (bd6a6051) Linux x64
Args: "bun" "run" "src/fixtest.ts"
Features: jsc transpiler_cache(2) tsconfig_paths tsconfig
Builtins: "bun:main" "node:buffer" "node:crypto" "node:dns" "node:events" "node:fs" "node:https" "node:net" "node:os" "node:path" "node:stream" "node:string_decoder" "node:tls" "node:url" "node:util" "node:util/types" "node:vm"
Elapsed: 80ms | User: 86ms | Sys: 0ms
RSS: 1.07GB | Peak: 91.56MB | Commit: 1.07GB | Faults: 0

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


[1]    9252 illegal hardware instruction  bun run src/fixtest.ts
➜  Backend git:(ink/messages) ✗

Stack Trace (bun.report)

Bun v1.1.13 (bd6a605) on linux x86_64 [RunCommand]

Segmentation fault at address 0x00000020

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

[Jarred-Sumner]

Duplicate of #11882

[Jarred-Sumner]

We are tracking this in #11882, please follow along in that issue