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

Terminal lets itself get killed by Application Hang #20722

New Issue
Closed
opened 2026-01-31 07:22:12 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:22:12 +00:00
Owner
Copy Link

Originally created by @binki on GitHub (Oct 23, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.2283

Other Software

No response

Steps to reproduce

  1. Have a Terminal open.
  2. Access the system using Remote Desktop set to a different DPI so that things have to be rescaled upon connection.
  3. Perhaps open many tabs with lots of history and run other programs to generate memory pressure and activity so that connecting to RDP takes a minute or two before the system is usable.
  4. Leave the system running for a long time, letting it do power management things, such as over a weekend multiple times.

Expected Behavior

Terminal to continue running, just like conhost would. Terminal should be immune to these subjective assumptions made by Windows about whether or not an application is responding when the system is simply under heavy load preventing the application from being able to be responsive. It seems like, by being a “modern” app, it opts into being auto-killed by Windows when it is “(Not Responding)” instead of being allowed to wait for whatever resource it is blocking on and allowed to continue living like conhost is.

Defaulting this as the default Terminal app in Windows and hiding conhost behind “Privacy & security / For developers” in Settings means that you intend for this to actually be as functional and reliable as conhost.

Actual Behavior

All of my terminal instances were closed. It wasn’t even just one window or one tab; all unrelated Terminal windows were closed. I found these two entries in the Windows Event Log:

The program WindowsTerminal.exe version 1.17.2305.26001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

Fault bucket 1632722192260213151, type 5
Event Name: MoAppHang
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.17.2305.26001
P4: 647122fe
P5: 0c21
P6: 2097152
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4363df2c-207e-4d28-af70-83dcbcda18b8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.49f2f45e-fef0-42a0-b2e2-5aaca38a5543.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c699f788-3e65-42f0-a497-a6b08c47c9ba.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f2f23b51-70a2-4425-a983-e999de1bb0c4.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Microsoft.Window_e72fc5e2ce25cf44cbc7da3e5ca2de47855cbe94_4fbd145a_921c5293-1263-484c-854d-4e9e567fb43f

Analysis symbol: 
Rechecking for solution: 0
Report Id: c659d0b0-b332-4256-bc27-18bd8d87ef84
Report Status: 268435456
Hashed bucket: 33e0e3ff5ea1cdbc26a8982eee91299f
Cab Guid: 0

This is a similar issue to #3915 in terms of the potential for work lost, state lost, and frustration caused. Personally, I am fine with Windows automatically rebooting for updates. But when I access the system and I can tell it didn’t reboot, I expect all of my applications to still be there. When all of my Terminal windows are mysteriously gone, that is just weird. There wasn’t a reboot, so it didn’t need to be killed. This is purely just a waste of time because a subjective test based on system performance determined that the application should be autokilled (I presume—unless if it is actually hung—but since it is autokilled I have no chance to tell if that is the case).

Originally created by @binki on GitHub (Oct 23, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621.2283 ### Other Software _No response_ ### Steps to reproduce 1. Have a Terminal open. 2. Access the system using Remote Desktop set to a different DPI so that things have to be rescaled upon connection. 3. Perhaps open many tabs with lots of history and run other programs to generate memory pressure and activity so that connecting to RDP takes a minute or two before the system is usable. 4. Leave the system running for a long time, letting it do power management things, such as over a weekend multiple times. ### Expected Behavior Terminal to continue running, just like conhost would. Terminal should be immune to these subjective assumptions made by Windows about whether or not an application is responding when the system is simply under heavy load preventing the application from being able to be responsive. It seems like, by being a “modern” app, it opts into being auto-killed by Windows when it is “(Not Responding)” instead of being allowed to wait for whatever resource it is blocking on and allowed to continue living like conhost is. Defaulting this as the default Terminal app in Windows and hiding conhost behind “Privacy & security / For developers” in Settings means that you intend for this to actually be as functional and reliable as conhost. ### Actual Behavior All of my terminal instances were closed. It wasn’t even just one window or one tab; all unrelated Terminal windows were closed. I found these two entries in the Windows Event Log: ``` The program WindowsTerminal.exe version 1.17.2305.26001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. ``` ``` Fault bucket 1632722192260213151, type 5 Event Name: MoAppHang Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe P2: praid:App P3: 1.17.2305.26001 P4: 647122fe P5: 0c21 P6: 2097152 P7: P8: P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4363df2c-207e-4d28-af70-83dcbcda18b8.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.49f2f45e-fef0-42a0-b2e2-5aaca38a5543.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c699f788-3e65-42f0-a497-a6b08c47c9ba.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f2f23b51-70a2-4425-a983-e999de1bb0c4.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Microsoft.Window_e72fc5e2ce25cf44cbc7da3e5ca2de47855cbe94_4fbd145a_921c5293-1263-484c-854d-4e9e567fb43f Analysis symbol: Rechecking for solution: 0 Report Id: c659d0b0-b332-4256-bc27-18bd8d87ef84 Report Status: 268435456 Hashed bucket: 33e0e3ff5ea1cdbc26a8982eee91299f Cab Guid: 0 ``` This is a similar issue to #3915 in terms of the potential for work lost, state lost, and frustration caused. Personally, I am fine with Windows automatically rebooting for updates. But when I access the system and I can tell it didn’t reboot, I expect all of my applications to still be there. When all of my Terminal windows are mysteriously gone, that is just weird. There wasn’t a reboot, so it didn’t *need* to be killed. This is purely just a waste of time because a subjective test based on system performance determined that the application should be autokilled (I presume—unless if it is actually hung—but since it is autokilled I have no chance to tell if that is the case).
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:22:12 +00:00
claunia commented 2026-01-31 07:22:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2023):

Undoubtably, this is the Store update thing. What version of the Terminal do you have now? 1.18 just started rolling out broadly about one week ago, and we're always get these sorts of posts about 7 days later.

@zadjii-msft commented on GitHub (Oct 23, 2023): Undoubtably, this is the Store update thing. What version of the Terminal do you have now? 1.18 just started rolling out broadly about one week ago, and we're always get these sorts of posts about 7 days later.
claunia commented 2026-01-31 07:22:14 +00:00
Author
Owner
Copy Link

@binki commented on GitHub (Oct 23, 2023):

Does store actually cause Application Hang? That seems weird.

@binki commented on GitHub (Oct 23, 2023): Does store actually cause Application Hang? That seems weird.
claunia commented 2026-01-31 07:22:14 +00:00
Author
Owner
Copy Link

@binki commented on GitHub (Oct 23, 2023):

But it is true that now Terminal reports its version as 1.18.2822.0 whereas the crash is from 1.17.11461.0.

@binki commented on GitHub (Oct 23, 2023): But it is true that now Terminal reports its version as 1.18.2822.0 whereas the crash is from 1.17.11461.0.
claunia commented 2026-01-31 07:22:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2023):

Yep, then this is definitely /dup #3915. Only in the latest Windows 11 builds (literally, the most recent release) did the Store add the ability to opt-out of that behavior.

Thanks!

@zadjii-msft commented on GitHub (Oct 23, 2023): Yep, then this is definitely /dup #3915. Only in the latest Windows 11 builds (literally, the most recent release) did the Store add the ability to opt-out of that behavior. Thanks!
claunia commented 2026-01-31 07:22:14 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 23, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- 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 Issue-Bug Resolution-Duplicate
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#20722
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?