Crash after a few days running inside docker

[ttmx]

How can we reproduce the crash?

https://github.com/carrismetropolitana/discord-bot Running the previous software in docker compose for multiple days.

There was nothing in specific that seemed to trigger the crash.

Relevant log output

Bun v1.1.17 (bb66bba1) Linux x64 (baseline)
Linux Kernel v6.5.0 | glibc v2.31
Args: "bun" "run" "index.js"
Features: jsc Bun.stdin(2) fetch(5757) WebSocket(51) 
Builtins: "bun:main" "bun:sqlite" "node:buffer" "node:events" "node:fs" "node:fs/promises" "node:http" "node:os" "node:path" "node:process" "node:string_decoder" "node:timers" "node:timers/promises" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "undici" "ws" 
Elapsed: 341182632ms | User: 123978ms | Sys: 124518ms
RSS: 0.88GB | Peak: 0.18GB | Commit: 0.88GB | Faults: 27
panic(main thread): Segmentation fault at address 0x0
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:

Stack Trace (bun.report)

Bun v1.1.17 (bb66bba) on linux x86_64_baseline [RunCommand]

Segmentation fault at address 0x00000000

• ld-temp.o:0: WTF::jscSignalHandler
• ??
• StringImpl.h:1154: Bun::formatStackTrace
• ZigGlobalObject.cpp:571: computeErrorInfoWithoutPrepareStackTrace
• ZigGlobalObject.cpp:663: computeErrorInfoWrapper
• Function.h:53: WTF::Detail::CallableWrapper<WTF::String (...)(...), WTF::String, JSC::VM&, WTF::Vector<JSC::StackFrame, 0ul, WTF::CrashOnOverflow, 16ul, WTF::FastMalloc>&, unsigned int&, unsigned int&, WTF::String&, JSC::JSObject*>::call
• ld-temp.o:0: JSC::ErrorInstance::computeErrorInfo
• ld-temp.o:0: JSC::Heap::runEndPhase
• ld-temp.o:0: JSC::Heap::runCurrentPhase
• ld-temp.o:0: WTF::ScopedLambdaFunctor<void (...), JSC::Heap::collectInMutatorThread()::$_0>::implFunction

[github-actions[bot]]

@ttmx, the latest version of Bun is v1.1.20, but this crash was reported on Bun v1.1.17.

Are you able to reproduce this crash on the latest version of Bun?

bun upgrade

[ttmx]

Since this is such a hard to reproduce bug, I can't know if it is still present in the newest version or not. Either way, I have just updated.

[cirospaciari]

Fixed by https://github.com/oven-sh/bun/issues/11568