One time segmentation fault error

[lawrencecchen]

How can we reproduce the crash?

This only happened once, and I'm unable to reproduce this. Hopefully the stack trace is helpful.

JavaScript/TypeScript code that reproduces the crash?

No response

Relevant log output

Deploying manaflow...
============================================================
Bun v1.1.8 (89d25807) macOS Silicon
Args: "bun", "run", "deploy-partykit.ts"
Features: jsc Bun.stderr Bun.stdout dotenv shell spawn tsconfig_paths tsconfig(2) 
Builtins: "bun:main" "node:buffer" "node:crypto" "node:fs" "node:os" "node:path" "node:string_decoder" "node:util/types" 
Elapsed: 348ms | User: 28ms | Sys: 33ms
RSS: 40.76MB | Peak: 40.76MB | Commit: 1.07GB | Faults: 1220

panic(main thread): Segmentation fault at address 0x8
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.8/Mr189d2580A2oggsG__2m2kP2m2kP2m2kPu/krEull7H+o2pgB_u17kpCA2AQ

Stack Trace (bun.report)

Bun v1.1.8 (89d2580) on macos aarch64 [RunCommand]

Segmentation fault at address 0x00000008

• 2 unknown/js code
• src.shell.interpreter.Interpreter.Pipeline.start
• src.shell.interpreter.Interpreter.Pipeline.start
• src.shell.interpreter.Interpreter.Pipeline.start
• src.shell.interpreter.throwShellErr
• napi_create_uint32
• StatWatcher__create
• 1 unknown/js code
• llint_entry

[xela7]

i'm getting something very similar to this as well.

Bun v1.1.8 (89d2580) on macos x86_64 [TestCommand]

Segmentation fault at address 0x0000001A

• 3 unknown/js code
• vmEntryToJavaScript
• JSC::Interpreter::executeCall
• JSC::runJSMicrotask
• JSC::VM::drainMicrotasks
• Bun::jsFunctionReportUncaughtException
• 1 unknown/js code
• llint_entry

i notice also that in my .bin/bun file i have the following line:

"$basedir/../../../../node_modules/.pnpm/bun@1.1.8/node_modules/bun/bin/bun.exe" "$@"

Is this correct for a macOS install?

I get: panic(main thread): Segmentation fault at address 0x1A

[Jarred-Sumner]

@lawrencecchen I think #11165 will fix this