Segfault when using Prisma in workers on windows

[KilianB]

How can we reproduce the crash?

Clone https://github.com/KilianB/BunWorkerCrash and run.
I tried version 1.26 as well as the current canary and both are crashing on windows. Ubuntu works fine.

Relevant log output

No response

Stack Trace (bun.report)

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

Segmentation fault at address 0xFFFFFFFFFFFFFFFF

• napi.cpp:151: Zig::NapiFinalizer::call
• 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]

This might be a race condition. Defering terminating the workers for a few seconds with worker.terminate() does not result in a crash

[KilianB]

Added a reproduction repository and checked that it runs on Linux. It's only crashing on windows. You might need to run the code few times for it to happen. The higher the worker count the more likely it is to fail

[Jarred-Sumner]

Tracking this in #15964