The Silent Deadlock: Diagnosing Node.js Child Process Buffer Starvation
Why our background runner froze without logging an error, and how separating spawn() stream consumption from exec() cured it
Long-running automation runners spawned with piped stdio hung indefinitely when high-volume output went unconsumed or descendant processes kept inherited pipe descriptors open.
Distinguishing spawn() unmanaged pipe backpressure from exec() maxBuffer termination—and consuming stdout/stderr asynchronously on spawn() with detached stdio boundaries—eliminated the silent hang.