Segfault when using workers - Githubissues

oven-sh / bun

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one

https://bun.sh

Other

73.62k stars 2.72k forks source link

Segfault when using workers #14331

Closed KilianB closed 6 days ago

KilianB commented 6 days ago

How can we reproduce the crash?

I can not share a reasonable reproduction. 4 workers with a prisma and redis connection are spawned. This example segfaults 100% of the time.

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.30-canary (39b1c01) on windows x86_64 [RunCommand]

Segmentation fault at address 0x14A0000014A

1 unknown/js code
WeakSetInlines.h:53: JSC::WeakBlock::finalize
WeakSet.h:71: JSC::WeakSet::forEachBlock
MarkedSpace.cpp:213: JSC::MarkedSpace::lastChanceToFinalize
Vector.h:799: WTF::Vector<JSC::WeakBlock *,0,WTF::CrashOnOverflow,16,WTF::FastMalloc>::isEmpty
VM.cpp:498: JSC::VM::~VM
VM.h:288: JSC::VM::operator delete
uws.zig:4410: onThreadExit
web_worker.zig:369: spin
bindings.cpp:4874: JSC__VM__holdAPILock

Features: workers_spawned, workers_terminated, dotenv, jsc, transpiler_cache, tsconfig, tsconfig_paths, tsconfig_paths

KilianB commented 6 days ago

https://github.com/oven-sh/bun/issues/14332 has a better stack trace