Shell commands can hang on Windows after process exit #29822

Activity

1. github-actions

   assigned

   Hona

   on May 29, 2026
2. github-actions commented on May 29, 2026

   

   github-actionsBot

   on May 29, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • The Operating System field is empty (_No response_) — this is particularly important for a Windows-specific bug report. Please specify your exact Windows version (e.g., Windows 11 24H2).
   • The Terminal field is also empty — please specify which terminal you are using (e.g., Windows Terminal, PowerShell, cmd).
   • Steps to reproduce is listed as "Completely random" — please try to provide any additional context that might help narrow down when this occurs (e.g., specific command types, shell configuration, project size).

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Bug: bash tool hangs on Windows when grandchild process inherits stdout pipe #24784: Bash tool hangs on Windows when grandchild process inherits stdout pipe — describes the same symptom with a specific root cause analysis (grandchild processes keeping pipe handles open)
   • Bash tool hangs on Windows when command spawns detached child processes (e.g. playwright-cli) #24731: Bash tool hangs on Windows when command spawns detached child processes — same hang behavior on Windows with detached child processes
   • Windows: terminal tool stays in thinking state after dotnet build completes successfully #24926: Windows terminal tool stays in thinking state after dotnet build completes successfully — same symptom on Windows after process exit
   • bash tool hangs when command spawns background child processes #20902: bash tool hangs when command spawns background child processes — related hanging behavior with background processes

   If you believe this was flagged incorrectly, please let a maintainer know.
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   and removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on May 29, 2026
4. github-actions commented on May 29, 2026

   

   github-actionsBot

   on May 29, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue! It now meets the contributing guidelines and has been marked as compliant.
5. github-actions commented on Jul 29, 2026

   

   github-actionsBot

   on Jul 29, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
6. github-actions

   closed this as not plannedon Jul 29, 2026
7. gterminator commented on Sep 4, 2026

   

   gterminator

   on Sep 4, 2026

   More actions

   the pipe draining on powershell still exists.