2 people reported

All time, since Oct 8.

Panic on thread EAGAIN

“Like Node.js: child_process.spawn/spawnSync report EAGAIN as an error the program can handle, and an idle process keeps running.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/7470/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Process aborts with panic when thread creation fails with EAGAIN. Triggered when a container is at its pids.max or RLIMIT_NPROC is reached, even while idle.

Is this your bug?

File my report
Where
Runtime process
Error text
node[64869]: pthread_create: Resource temporarily unavailable
Versions
1.4.2 to 1.4.3-canary.1
Platforms
Linux
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Long bun test --isolate runs crash with SIGILL mid-run1 person
  2. Test workers segfault2 people
  3. Parallel test worker hangs2 people

Original reports2, newest first

  1. Crash on startup under thread exhaustion: pthread_create EAGAIN panics instead of failing cleanly (1.4.2, linux-x64)#46546
  2. Bun aborts (panic: abort() called) when it cannot create a thread (EAGAIN), even while idle; Node reports spawn EAGAIN as an error#44787

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.