starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Random crash due to process closing too fast #20321

New Issue
Closed
opened 2026-01-31 07:10:08 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:10:08 +00:00
Owner
Copy Link

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:08 +00:00
claunia commented 2026-01-31 07:10:09 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 2, 2023):

I've updated your comment with the Windows Terminal and Windows version numbers from your eventlog.zip. Please always add them to your bug reports. I've also included steps to restore the proper IPv6 policies.

Your command

Invoke-Command -ComputerName $servers -Credential $cred -ScriptBlock {

won't work because we don't have access to your $servers. I tried reproducing the issue in Windows Terminal 1.17.11461.0 without the two arguments (= locally) and the issue didn't occur. This implies to me that your repro steps really only work if an Invoke-Command is used on a remote machine.

How does Invoke-Command work on a remote machine? Does it spawn a Windows Terminal window on the remote and that's why it breaks?

@lhecker commented on GitHub (Aug 2, 2023): I've updated your comment with the Windows Terminal and Windows version numbers from your eventlog.zip. Please always add them to your bug reports. I've also included steps to restore the proper IPv6 policies. --- Your command ```pwsh Invoke-Command -ComputerName $servers -Credential $cred -ScriptBlock { ``` won't work because we don't have access to your `$servers`. I tried reproducing the issue in Windows Terminal 1.17.11461.0 without the two arguments (= locally) and the issue didn't occur. This implies to me that your repro steps really only work if an `Invoke-Command` is used on a remote machine. How does `Invoke-Command` work on a remote machine? Does it spawn a Windows Terminal window on the remote and that's why it breaks?
claunia commented 2026-01-31 07:10:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 2, 2023):

Honestly, the fastest way to a root cause might be a crash dump. Either via feedback hub:

/feedback

Or manually: https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capturing-and-sending-dumps

@zadjii-msft commented on GitHub (Aug 2, 2023): Honestly, the fastest way to a root cause might be a crash dump. Either via feedback hub: /feedback Or manually: https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capturing-and-sending-dumps
claunia commented 2026-01-31 07:10:10 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 2, 2023):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@microsoft-github-policy-service[bot] commented on GitHub (Aug 2, 2023): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 07:10:10 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 6, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 6, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20321
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?