starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows terminal crash #21111

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

Originally created by @NeilMacMullen on GitHub (Jan 19, 2024).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22631.0

Other Software

Custom application

Steps to reproduce

Unclear - still under investigation. Possible that application is experiencing OOM exception or generating large amounts or console output

Expected Behavior

Application should be terminated but terminal should keep running

Actual Behavior

We use Windows Terminal to spawn a number of powershell scripts in separate terminal processes. (The "master" script that does this simply invokes... Start-Process -windowstyle normal powershell -ArgumentList $arglist)

The poweshell scripts run some custom CLI commands periodically (i.e. they run the command then sleep for a few hours).

This results in a number of tiled windows....
image

Recently we have found instances where Terminal appears to crash in a way that the entire process is killed - i.e,. all spawned windows disappear. The trigger appears to be a fault in one of the CLI applications (possibly out-of-memory) but we would expect the behaviour in this case for the application to be killed, not the entire Terminal process. (Happy to close though if this is "expected" behaviour.)

Unfortunately we don't have a lot of post-mortem information at this time... EventLog shows an Application Error for Terminal...

Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e
Faulting module name: ntdll.dll, version: 10.0.22621.2506, time stamp: 0xbced4b82
Exception code: 0xc0000409
Fault offset: 0x00000000000a7d18
Faulting process ID: 0x0x5714
Faulting application start time: 0x0x1DA491FE3458FB2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 2082cf3e-3952-4061-bfe1-e6bc7aa7bef6
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Originally created by @NeilMacMullen on GitHub (Jan 19, 2024). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.22631.0 ### Other Software Custom application ### Steps to reproduce Unclear - still under investigation. Possible that application is experiencing OOM exception or generating large amounts or console output ### Expected Behavior Application should be terminated but terminal should keep running ### Actual Behavior We use Windows Terminal to spawn a number of powershell scripts in separate terminal processes. (The "master" script that does this simply invokes... `Start-Process -windowstyle normal powershell -ArgumentList $arglist`) The poweshell scripts run some custom CLI commands periodically (i.e. they run the command then sleep for a few hours). This results in a number of tiled windows.... ![image](https://github.com/microsoft/terminal/assets/9131337/85a7800a-8a9a-4275-b4f7-77ab8711693c) Recently we have found instances where Terminal appears to crash in a way that the entire process is killed - i.e,. all spawned windows disappear. The trigger appears to be a fault in one of the CLI applications (possibly out-of-memory) but we would expect the behaviour in this case for the _application_ to be killed, not the entire Terminal process. (Happy to close though if this is "expected" behaviour.) Unfortunately we don't have a lot of post-mortem information at this time... EventLog shows an Application Error for Terminal... ``` Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e Faulting module name: ntdll.dll, version: 10.0.22621.2506, time stamp: 0xbced4b82 Exception code: 0xc0000409 Fault offset: 0x00000000000a7d18 Faulting process ID: 0x0x5714 Faulting application start time: 0x0x1DA491FE3458FB2 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 2082cf3e-3952-4061-bfe1-e6bc7aa7bef6 Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-31 07:33:29 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 19, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Jan 19, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Windows Terminal crashes when opened (#11241)](https://github.com/microsoft/terminal/issues/11241), similarity score: 0.93 - [Windows Terminal Crashed abruptly. (#7861)](https://github.com/microsoft/terminal/issues/7861), similarity score: 0.93 - [Windows Terminal Crashes on Startup (#15792)](https://github.com/microsoft/terminal/issues/15792), similarity score: 0.90 - [Terminal crashes Windows 10X (#9433)](https://github.com/microsoft/terminal/issues/9433), similarity score: 0.89 - [crash with terminal (#9411)](https://github.com/microsoft/terminal/issues/9411), similarity score: 0.87 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:33:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 19, 2024):

Hmm. That Report ID isn't on the backend, at least not that I can find it. Did you happen to see a Bucket ID anywhere? Otherwise, reproing this with Feedback Hub is probably the easiest way for us to get to the crash dump: /feedback

@zadjii-msft commented on GitHub (Jan 19, 2024): Hmm. That Report ID isn't on the backend, at least not that I can find it. Did you happen to see a Bucket ID anywhere? Otherwise, reproing this with Feedback Hub is probably the easiest way for us to get to the crash dump: /feedback
claunia commented 2026-01-31 07:33:29 +00:00
Author
Owner
Copy Link

@NeilMacMullen commented on GitHub (Jan 19, 2024):

Hmm - I can't find a "bucketid" anywhere but in case it's helpful here are a couple more reports of what look like the same problem....


Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000c5d2eff8a8
Faulting process ID: 0x0x63D4
Faulting application start time: 0x0x1DA4ABDD38785BE
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: unknown
Report ID: 0cb28a16-b300-490e-84b2-69e2eacda35f
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000005dd9cff238
Faulting process ID: 0x0x66C
Faulting application start time: 0x0x1DA485787FEEE27
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: unknown
Report ID: 53e775d3-23ed-4aab-ad06-2c591707647a
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Unfortunately I haven't yet found a way to reliably reproduce this on demand but will continue investigating.

@NeilMacMullen commented on GitHub (Jan 19, 2024): Hmm - I can't find a "bucketid" anywhere but in case it's helpful here are a couple more reports of what look like the same problem.... ``` Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000000c5d2eff8a8 Faulting process ID: 0x0x63D4 Faulting application start time: 0x0x1DA4ABDD38785BE Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: unknown Report ID: 0cb28a16-b300-490e-84b2-69e2eacda35f Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` ``` Faulting application name: WindowsTerminal.exe, version: 1.18.2311.14001, time stamp: 0x6553b19e Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000005dd9cff238 Faulting process ID: 0x0x66C Faulting application start time: 0x0x1DA485787FEEE27 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: unknown Report ID: 53e775d3-23ed-4aab-ad06-2c591707647a Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Unfortunately I haven't yet found a way to reliably reproduce this on demand but will continue investigating.
claunia commented 2026-01-31 07:33:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 24, 2024):

We've got a theory here that this might be the same thing that #16575 is supposed to fix. We're planning on merging that and quickly pushing an updated build Soon. We should be able to give you a build with some fixes and tease out if that's the actual same root cause or not.

@zadjii-msft commented on GitHub (Jan 24, 2024): We've got a theory here that this might be the same thing that #16575 is supposed to fix. We're planning on merging that and quickly pushing an updated build Soon<tm>. We should be able to give you a build with some fixes and tease out if that's the actual same root cause or not.
claunia commented 2026-01-31 07:33:30 +00:00
Author
Owner
Copy Link

@NeilMacMullen commented on GitHub (Jan 24, 2024):

Interesting. In typical fashion the system has now been running fine for 4 days without re-exhibiting the problem after I added extra diagnostics to try and track down the precipitating event. I couldn't quite follow the discussion in the referenced bug but looks like this is triggered by a (heavily multi-threaded ?) app crash? That might well be consistent with what we're doing.

@NeilMacMullen commented on GitHub (Jan 24, 2024): Interesting. In typical fashion the system has now been running fine for 4 days without re-exhibiting the problem after I added extra diagnostics to try and track down the precipitating event. I couldn't quite follow the discussion in the referenced bug but looks like this is triggered by a (heavily multi-threaded ?) app crash? That might well be consistent with what we're doing.
claunia commented 2026-01-31 07:33:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 6, 2024):

If this is cool with you, I'm gonna close this out for housekeeping. If you ever see it again, we can always reopen ☺️

@zadjii-msft commented on GitHub (Feb 6, 2024): If this is cool with you, I'm gonna close this out for housekeeping. If you ever see it again, we can always reopen ☺️
claunia commented 2026-01-31 07:33:30 +00:00
Author
Owner
Copy Link

@NeilMacMullen commented on GitHub (Feb 6, 2024):

hmm- I've seen it 4 or 5 times since but unfortunately it's very difficult to reproduce on demand - normally I come back to the machine after a couple of days and notice it has occurred. I'm happy to try out whichever build contains the fix for #16575 though and can let you know if that makes it go away.

@NeilMacMullen commented on GitHub (Feb 6, 2024): hmm- I've seen it 4 or 5 times since but unfortunately it's very difficult to reproduce on demand - normally I come back to the machine after a couple of days and notice it has occurred. I'm happy to try out whichever build contains the fix for #16575 though and can let you know if that makes it go away.
claunia commented 2026-01-31 07:33:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 7, 2024):

Gotcha. Okay I'll reopen then. The 1.19 Stable release should have that fix in it - lmk if it comes back? (or, I'll have the bot re-close if it has just gone away ☺️ )

@zadjii-msft commented on GitHub (Feb 7, 2024): Gotcha. Okay I'll reopen then. The 1.19 Stable release should have that fix in it - lmk if it comes back? (or, I'll have the bot re-close if it has just gone away ☺️ )
claunia commented 2026-01-31 07:33:31 +00:00
Author
Owner
Copy Link

@NeilMacMullen commented on GitHub (Feb 7, 2024):

Great - I've upgraded to Windows Terminal Preview Version: 1.20.10303.0. Fingers crossed it's gone away but if not I'll dig in a bit further and let you know of any evidence I can collect.

@NeilMacMullen commented on GitHub (Feb 7, 2024): Great - I've upgraded to Windows Terminal Preview Version: 1.20.10303.0. Fingers crossed it's gone away but if not I'll dig in a bit further and let you know of any evidence I can collect.
claunia commented 2026-01-31 07:33:31 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 12, 2024):

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 (Feb 12, 2024): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Area-DefApp Issue-Bug Needs-Attention Needs-Author-Feedback Needs-Repro No-Recent-Activity Priority-1 Product-Terminal Severity-Crash
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#21111
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?