Bun.spawnSync segfaults on Windows macro

[gitblit]

What version of Bun is running?

1.1.4+fbe2fe0c3

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What steps can reproduce the bug?

index.ts

import { getGitCommitHash } from "./utils" with { type: "macro" };

console.log(`The current git commit is ${getGitCommitHash()}`);

utils.ts

// Bun build macro
export function getGitCommitHash() {
    const { stdout } = Bun.spawnSync({
      cmd: ["git", "rev-parse", "HEAD"],
      stdout: "pipe",
    });

    return stdout.toString().trim();
  }

console

bun run dev

What is the expected behavior?

Console should display:

The current git commit is 62b56d4e169308b2d4d96b3b6deb3118240dcdde

What do you see instead?

$ bun run --watch src/index.ts
Segmentation fault at address 0x68
???:?:?: 0x7ff61c1f89da in ??? (bun.exe)
???:?:?: 0x7ff61c1f7010 in ??? (bun.exe)
???:?:?: 0x1a59abc119d in ??? (???)
???:?:?: 0x425f56d043 in ??? (???)
???:?:?: 0x1a5989873cf in ??? (???)
???:?:?: 0x1a5988e096f in ??? (???)
error: script "dev" exited with code 3

Additional information

If I remove the syntax with { type: "macro" }, then it succeeds.

[gitblit]

Updated with crash reporter data introduced in 1.1.5.

Bun v1.1.5 (#10527) on windows x86_64 [RunCommand]

Segmentation fault at address 0x00000068

• event_loop.zig:2168: loop
• Allocator.zig:86: rawAlloc
• types.zig:1086: eat
• 4 unknown/js code
• [xcall_once.h:94](https://github.com/oven-sh/bun/blob/b257a309772db2e9dfb745f97068aea6a32ca151/C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.38.33130/include/xcall_once.h#L94): std::_Init_once_completer::~_Init_once_completer
• llint_entry
• 1 unknown/js code

[gitblit]

Updated with crash reporter data from 1.1.8.

Bun v1.1.8 (89d2580) on windows x86_64 [RunCommand]

Segmentation fault at address 0x00000078

• process.zig:1519: spawnProcessWindows
• process.zig:1189: spawnProcess
• base.zig:1501: method
• 2 unknown/js code
• LLIntEntrypoint.cpp:70: JSC::LLInt::setFunctionEntrypoint
• 4 unknown/js code

[gitblit]

This appears to have been resolved sometime between version1.1.8 and 1.1.26.