seg fault Windows

[4cecoder]

How can we reproduce the crash?

Just running any bun command

Relevant log output

Bun Canary v1.1.19-canary.1 (b7dd57ac) Windows x64
CPU: sse42 avx avx2
Args: "C:\Users\fource\scoop\apps\bun-canary\current\bun.exe" "upgrade"
Elapsed: 95ms | User: 0ms | Sys: 0ms
RSS: 54.33MB | Peak: 54.33MB | Commit: 110.44MB | Faults: 13462

panic(thread 11008): 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:

 https://bun.report/1.1.19/wp2b7dd57aAACa\MSVCP140.dllgr3Eyiln3C8x7rc6o5rci5m7ak49xWCa\KERNEL32.DLL63yECU\ntdll.dllwy3WA2AA

Stack Trace (bun.report)

Bun v1.1.19 (b7dd57a) on windows x86_64 [UpdateCommand]

Segmentation fault at address 0x00000000

• ??? at 0x12eb0 in MSVCP140.dll
• [mutex:52](<https://github.com/oven-sh/bun/blob/b7dd57ac32bb120177ce5f3da1bedd1414743d37/C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/include/mutex#L52>): std::_Mutex_base::lock
• ??
• uv_run
• http.zig:925: processEvents
• http.zig:814: onStart
• ??? at 0x1257d in KERNEL32.DLL
• ??? at 0x5af28 in ntdll.dll

[Jarred-Sumner]

can you download bun-windows-x64 from this CI run and let us know if the issue reproduces on this commit?

https://github.com/oven-sh/bun/actions/runs/9885336885

[sequencerr]

[sequencerr]

@Jarred-Sumner

[Jarred-Sumner]

There’s definitely no password, try using 7zip

[sequencerr]

Uhh thats was weird

ok thats what I got

PS D:\Projects\Plugins\bun-repro-postinstall> d:\Downloads\bun-windows-x64\bun-windows-x64\bun.exe i                                          
bun install v1.1.19-canary.1 (58483426)
  🔍 Resolving [1/1] ============================================================
Bun Canary v1.1.19-canary.1 (58483426) Windows x64
CPU: sse42 avx avx2
Args: "D:\Downloads\bun-windows-x64\bun-windows-x64\bun.exe" "i"       
Elapsed: 32ms | User: 31ms | Sys: 46ms
RSS: 64.35MB | Peak: 64.36MB | Commit: 111.32MB | Faults: 15938

panic(thread 3300): 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:

 https://bun.report/1.1.19/wi25848342AACa\MSVCP140.dllw13Eyy+o3C8h1tc64ytci7/8aki2zWCa\KERNEL32.DLLo05FCU\ntdll.dllipmTA2AA

[sequencerr]

@Jarred-Sumner 🙏🏼

[sequencerr]

may I force reinstall?

[4cecoder]

can you download bun-windows-x64 from this CI run and let us know if the issue reproduces on this commit?

https://github.com/oven-sh/bun/actions/runs/9885336885

How do I test the binaries from this commit ID?

Can you give me a tutorial if I have to build from source from this commit ID?

Just let me know the zig command or whatever is needed to run it from this commit ID that you suggested. Thank you.

[sequencerr]

@4cecoder that's link to deploy workflow and there is already build binary (called artifact) which we are asked to download

[Msfrhdsa]

can you download bun-windows-x64 from this CI run and let us know if the issue reproduces on this commit?

https://github.com/oven-sh/bun/actions/runs/9885336885

No, it doesn't work. Same error as there was.

[Msfrhdsa]

I tried all versions - they all have errors and simply don't launch. So I understand there is no real possibility of fixing this in the near future. Funny bun, kek

[sequencerr]

well using powershell script to upgrade should fix. but reason of this bug seems to be unknown

[4cecoder]

well using powershell script to upgrade should fix. but reason of this bug seems to be unknown

I can't find any casual issue for the bug internally either

Maybe it's a deeply windows behavior... Maybe from indexing? Or something else troubling usually due to windows systems