The catch in sweepWindowsPtyHosts treated every error as "process exited", including EPERM. On Windows EPERM means the pty-host exists but the caller lacks permission to signal it (cross-context), so the orphan was skipping the killProcessTree force-kill step and leaking. Mirror the destroy() logic at line 290: only flag exited on non-EPERM (typically ESRCH). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| src | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||