bun crash

[prasui2522]

How can we reproduce the crash?

No response

Relevant log output

Stack Trace (bun.report)

Bun v1.2.16 (631e674) on windows x86_64 [RunAsNodeCommand]

Segmentation fault at address 0x00000010

• BunClientData.h:141: WTF::TypeCastTraits<const WebCore::JSVMClientData,const JSC::VM::ClientData,0>::isType
• JSGlobalObject.zig:609: bunVMConcurrently
• memory:3426: std::unique_ptr<WTF::Detail::CallableWrapperBase<void,WebCore::ScriptExecutionContext &>,std::default_delete<WTF::Detail::CallableWrapperBase<void,WebCore::ScriptExecutionContext &> > >::~unique_ptr
• signal.c:251: uv__process_signal_req
• req-inl.h:193: uv__process_reqs
• core.c:657: uv_run
• VirtualMachine.zig:308: onAfterEventLoop
• bun_js.zig:409: start
• bindings.cpp:5236: JSC__VM__holdAPILock
• VM.zig:41: holdAPILock

Features: transpiler_cache, tsconfig, tsconfig_paths, process_dlopen, Bun.stderr, Bun.stdout, dotenv, jsc, spawn

_{Sentry Issue: BUN-N2D}

[github-actions]

@prasui2522, the latest version of Bun is v1.2.17, but this crash was reported on Bun v1.2.16.

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

bun upgrade

[github-actions]

Hello @prasui2522. Please provide a minimal reproduction using a GitHub repository, Replit, CodeSandbox, or provide a bulleted list of commands to run that reproduce this issue. Issues marked with needs repro will be closed if they have no activity within 3 days.