Random crash due to process closing too fast #20318

Open
opened 2026-01-31 07:10:05 +00:00 by claunia · 0 comments
Owner

Originally created by @wizpresso-steve-cy-fan on GitHub (Aug 2, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19041.3271

Other Software

No response

Steps to reproduce

Unknown, this is pretty much random. The fastest way to reproduce it is to run the following:

Invoke-Command -ComputerName $servers -Credential $cred -ScriptBlock {
    netsh interface ipv6 set prefixpolicy ::ffff:0:0/96 50 0
    netsh interface ipv6 set prefixpolicy ::1/128 40 1
    netsh interface ipv6 set prefixpolicy ::/0 30 2
    netsh interface ipv6 set prefixpolicy 2002::/16 20 3
    netsh interface ipv6 set prefixpolicy 2001::/32 5 5
    netsh interface ipv6 set prefixpolicy fc00::/7 3 13
    netsh interface ipv6 set prefixpolicy fec0::/10 1 11
    netsh interface ipv6 set prefixpolicy 3ffe::/16 1 12
    netsh interface ipv6 set prefixpolicy ::/96 1 4
}

Run a lot of independent processes that closes quickly. Make sure Windows Terminal is set to the default console host.

NOTE: After testing, reset your policies with (for instance) netsh interface ipv6 reset and reboot. netsh interface ipv6 show prefixpolicies should produce:

Precedence  Label  Prefix
----------  -----  --------------------------------
        50      0  ::1/128
        40      1  ::/0
        35      4  ::ffff:0:0/96
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

Expected Behavior

No response

Actual Behavior

We noticed some of the crashing process reported 0x800700e8 (The pipe is being closed) and then crashes

eventlog.zip

Originally created by @wizpresso-steve-cy-fan on GitHub (Aug 2, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.19041.3271 ### Other Software _No response_ ### Steps to reproduce Unknown, this is pretty much random. The fastest way to reproduce it is to run the following: ```pwsh Invoke-Command -ComputerName $servers -Credential $cred -ScriptBlock { netsh interface ipv6 set prefixpolicy ::ffff:0:0/96 50 0 netsh interface ipv6 set prefixpolicy ::1/128 40 1 netsh interface ipv6 set prefixpolicy ::/0 30 2 netsh interface ipv6 set prefixpolicy 2002::/16 20 3 netsh interface ipv6 set prefixpolicy 2001::/32 5 5 netsh interface ipv6 set prefixpolicy fc00::/7 3 13 netsh interface ipv6 set prefixpolicy fec0::/10 1 11 netsh interface ipv6 set prefixpolicy 3ffe::/16 1 12 netsh interface ipv6 set prefixpolicy ::/96 1 4 } ``` Run a lot of independent processes that closes quickly. Make sure Windows Terminal is set to the default console host. **NOTE:** After testing, reset your policies with (for instance) `netsh interface ipv6 reset` and reboot. `netsh interface ipv6 show prefixpolicies` should produce: ``` Precedence Label Prefix ---------- ----- -------------------------------- 50 0 ::1/128 40 1 ::/0 35 4 ::ffff:0:0/96 30 2 2002::/16 5 5 2001::/32 3 13 fc00::/7 1 11 fec0::/10 1 12 3ffe::/16 1 3 ::/96 ``` ### Expected Behavior _No response_ ### Actual Behavior We noticed some of the crashing process reported 0x800700e8 (The pipe is being closed) and then crashes [eventlog.zip](https://github.com/microsoft/terminal/files/12235868/eventlog.zip)
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 07:10:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20318