Bug: spawn EBADF on every exec call — fresh install, macOS arm64
Version: 2026.2.6-3
OS: macOS Sequoia (Darwin 25.2.0, arm64)
Node: v25.3.0
Every exec/spawn call fails with spawn EBADF immediately — not after gradual FD exhaustion.
What I've tried:
Full gateway stop/start (multiple times)
pkill -f openclaw + fresh start
ulimit -n 10240 before starting
npm update -g openclaw
FD count after fresh start: only 52 (well under limit)
Node itself spawns fine: node -e "require('child_process').execSync('echo hello', {stdio:'pipe'})" works
Previous state: Before restart, lsof showed 10,507 open FDs with a ulimit of 256 — classic PTY leak. But even after killing everything and restarting with a high ulimit and only 52 FDs, exec still fails.
Seems related to PRs #4153 and #4932. Any workaround available before those land?
OS: macOS Sequoia (Darwin 25.2.0, arm64)
Node: v25.3.0
Every exec/spawn call fails with spawn EBADF immediately — not after gradual FD exhaustion.
What I've tried:
Full gateway stop/start (multiple times)
pkill -f openclaw + fresh start
ulimit -n 10240 before starting
npm update -g openclaw
FD count after fresh start: only 52 (well under limit)
Node itself spawns fine: node -e "require('child_process').execSync('echo hello', {stdio:'pipe'})" works
Previous state: Before restart, lsof showed 10,507 open FDs with a ulimit of 256 — classic PTY leak. But even after killing everything and restarting with a high ulimit and only 52 FDs, exec still fails.
Seems related to PRs #4153 and #4932. Any workaround available before those land?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
