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 app silently crashes #10225

New Issue
Open
opened 2026-01-31 02:15:48 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 02:15:48 +00:00
Owner
Copy Link

Originally created by @dbaines on GitHub (Aug 20, 2020).

Environment

Windows build number:  Microsoft Windows [Version 10.0.19042.450]
Windows Terminal version (if applicable): 1.1.2233.0

Any other software?
VS Code
MS Teams
Steam
Spotify
Chrome

Steps to reproduce

Not entirely sure what happened as it was a silent crash.
The system has been up for at least two days.
Terminal was running a java app via maven and a gulp watch in separate tabs

Expected behavior

If crashing, show an error with a possible message why

Actual behavior

Terminal app silently crashes showing no error

Event log

It did throw an event log which I can attach in full. I'm not sure if there's any security issues in doing so, I don't think it's a memory dump but I'm happy to forward to the secure email address if you like.
I think these parts from the event might be helpful:

Event log:

The program WindowsTerminal.exe version 1.1.2007.20001 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.
 ...
 Faulting package full name: Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe
 Faulting package-relative application ID: App
 Hang type: Quiesce

Problem history:

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

Problem signature
Problem Event Name:	MoAppHang
Package Full Name:	Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe
Application Name:	praid:App
Application Version:	1.1.2007.20001

Other

Might possibly be related to #7345 - but I didn't check if existing processes were still running, sorry. This crash occurred yesterday around 10am ACST.
Interestingly, the version reported in the event log doesn't match the version presented when opening Terminal's "about" screen - could it be related to a forced update closing terminal while still in use?

Originally created by @dbaines on GitHub (Aug 20, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19042.450] Windows Terminal version (if applicable): 1.1.2233.0 Any other software? VS Code MS Teams Steam Spotify Chrome ``` # Steps to reproduce Not entirely sure what happened as it was a silent crash. The system has been up for at least two days. Terminal was running a java app via maven and a gulp watch in separate tabs # Expected behavior If crashing, show an error with a possible message why # Actual behavior Terminal app silently crashes showing no error # Event log It did throw an event log which I can attach in full. I'm not sure if there's any security issues in doing so, I don't think it's a memory dump but I'm happy to forward to the secure email address if you like. I think these parts from the event might be helpful: Event log: ``` The program WindowsTerminal.exe version 1.1.2007.20001 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. ... Faulting package full name: Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Hang type: Quiesce ``` Problem history: ``` Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Problem signature Problem Event Name: MoAppHang Package Full Name: Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe Application Name: praid:App Application Version: 1.1.2007.20001 ``` # Other Might possibly be related to #7345 - but I didn't check if existing processes were still running, sorry. This crash occurred yesterday around 10am ACST. Interestingly, the version reported in the event log doesn't match the version presented when opening Terminal's "about" screen - could it be related to a forced update closing terminal while still in use?
claunia added the Resolution-Duplicate label 2026-01-31 02:15:48 +00:00
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 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#10225
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?