Segfault on large number of process spawns

[bwasti]

Version

0.2.1

Platform

Darwin bwasti-mbp 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000 arm64

What steps will reproduce the bug?

import { spawn } from "bun";

const t0 = performance.now()
const parallel = 1000 // this number needs to be big
let procs = []
for (let i = 0; i < parallel; ++i) {
  procs.push(new Response(spawn(["bun", "wrk.ts"]).stdout).text())
}

const texts = await Promise.all(procs);
const t1 = performance.now()
console.log(`done, ${parallel} parallel executions in`, (Math.round(t1 - t0))/1e3, 'seconds')

wrk.ts is:

function sleep(ms) {
    return new Promise(resolve => setTimeout(resolve, ms));
}
for (let i = 0; i < 20; ++i) {
  console.log(i)
  await sleep(50)
}

How often does it reproduce? Is there a required condition?

as long as parallel in the above code is somewhat unreasonably large (like 1000)

What is the expected behavior?

shouldn't segfault, but could throw an error saying "that's way too many processes to spawn"

What do you see instead?

Additional information

No response

[Jarred-Sumner]

This reads like a GC bug

If you assign the return value of spawn() to a unique global does it still segfault?

[cirospaciari]

@bwasti I was not able to reproduce on >= v0.5.9, Are you still able to reproduce this issue in the current version?

[Jarred-Sumner]

This was fixed some time ago

If you run into it again, please leave a comment