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

Windows Terminal v1.1.2233.0 disappears leaving all processes intact #10227

New Issue
Closed
opened 2026-01-31 02:15:50 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:15:50 +00:00
Owner
Copy Link

Originally created by @qm2k on GitHub (Aug 19, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2233.0

Any other software?

I'm using git bash as shell, but I don't think it's relevant.

Steps to reproduce

Keep Windows Terminal started for days with multiple tabs and some processes running inside (e.g. normal use mode).

Expected behavior

Windows Terminal not disappearing. As a workaround (since the problem may recur), if it closes it allows me to access all of my earlier started processes again after I restart the app.

Actual behavior

Windows Terminal disappears at some time while I'm not using my computer, leaving all started processes intact. When I relaunch it the Task Manager shows my previously started processes (immediate siblings only, not processes started from these processes) under the newly opened window, but the window itself only shows one default tab:
image
image

The symptoms are exactly repeating those described in #3253 that was supposed to be fixed in v0.7.3291.0

Originally created by @qm2k on GitHub (Aug 19, 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: 10.0.19041.0 Windows Terminal version (if applicable): 1.1.2233.0 Any other software? ``` I'm using [git bash](https://git-scm.com/download/win) as shell, but I don't think it's relevant. # Steps to reproduce Keep Windows Terminal started for days with multiple tabs and some processes running inside (e.g. normal use mode). # Expected behavior Windows Terminal not disappearing. As a workaround (since the problem may recur), if it closes it allows me to access all of my earlier started processes again after I restart the app. # Actual behavior Windows Terminal disappears at some time while I'm not using my computer, leaving all started processes intact. When I relaunch it the Task Manager shows my previously started processes (immediate siblings only, not processes started from these processes) under the newly opened window, but the window itself only shows one default tab: ![image](https://user-images.githubusercontent.com/13719792/90624354-7f40b780-e220-11ea-8b03-83cd38b1e9fc.png) ![image](https://user-images.githubusercontent.com/13719792/90624387-8b2c7980-e220-11ea-9805-be753bccb853.png) The symptoms are exactly repeating those described in #3253 that was supposed to be fixed in v0.7.3291.0
claunia added the Resolution-DuplicateProduct-TerminalSeverity-Crash labels 2026-01-31 02:15:50 +00:00
claunia commented 2026-01-31 02:15:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2020):

Well that's definitely unexpected. Especially the fact that Task manager can figure out that those child processes should be re-parented to the Windows Terminal package - if the original process were truly killed and cleaned up, then you'd imagine that there'd be no way of determining that.

Does this always take multiple days to reproduce? Or is there something that you can do to trigger this behavior on demand?

@zadjii-msft commented on GitHub (Aug 19, 2020): Well that's definitely unexpected. Especially the fact that Task manager can figure out that those child processes should be re-parented to the Windows Terminal package - if the original process were truly killed and cleaned up, then you'd imagine that there'd be no way of determining that. Does this always take multiple days to reproduce? Or is there something that you can do to trigger this behavior on demand?
claunia commented 2026-01-31 02:15:51 +00:00
Author
Owner
Copy Link

@qm2k commented on GitHub (Aug 20, 2020):

Does this always take multiple days to reproduce? Or is there something that you can do to trigger this behavior on demand?

It happened twice already. I found both corresponding windows log events. Previous time was 30/07/2020 04:27:26 and I was definitely not present at the computer. Yesterday it happened on 09:25 and I might have been present but I don't remember anything unusual (I'm using multiple desktops so it took me some time to notice that the terminal window missing). According to logs there was no windows update at the time, and automatic suspend on mains power was disabled (and I definitely did not wake the computer up, only unlocked the screen).

Here's the last event (also .xml and .evtx):

Logged: 19/08/2020 09:25:13
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.
Process ID: 52ec
Start Time: 01d6724a7dc40bd8
Termination Time: 4294967295
Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Report Id: 8a097a96-a30a-4804-b26e-61e690adf68a
Faulting package full name: Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Hang type: Quiesce

@qm2k commented on GitHub (Aug 20, 2020): > Does this always take multiple days to reproduce? Or is there something that you can do to trigger this behavior on demand? It happened twice already. I found both corresponding windows log events. Previous time was 30/07/2020 04:27:26 and I was definitely not present at the computer. Yesterday it happened on 09:25 and I might have been present but I don't remember anything unusual (I'm using multiple desktops so it took me some time to notice that the terminal window missing). According to logs there was no windows update at the time, and automatic suspend on mains power was disabled (and I definitely did not wake the computer up, only unlocked the screen). Here's the last event (also [.xml and .evtx](https://github.com/microsoft/terminal/files/5101711/1002_ApplicationHang.zip)): > Logged: 19/08/2020 09:25:13 > 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. > Process ID: 52ec > Start Time: 01d6724a7dc40bd8 > Termination Time: 4294967295 > Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Report Id: 8a097a96-a30a-4804-b26e-61e690adf68a > Faulting package full name: Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe > Faulting package-relative application ID: App > Hang type: Quiesce >
claunia commented 2026-01-31 02:15:51 +00:00
Author
Owner
Copy Link

@qm2k commented on GitHub (Aug 20, 2020):

Just noticed that versions in the version I'm currently running (1.1.2233.0, also latest in Microsoft Store) and the version in the event viewer do not match. Also found the following events from WindowsUpdateClient:

Logged: 19/08/2020 09:24:30
Installation Started: Windows has started installing the following update: 9N0DX20HK701-Microsoft.WindowsTerminal

Logged: 19/08/2020 09:25:14
Installation Successful: Windows successfully installed the following update: 9N0DX20HK701-Microsoft.WindowsTerminal

There was no system update, but apparently an app update happend sometime around the crash. Looks highly suspicious.

@qm2k commented on GitHub (Aug 20, 2020): Just noticed that versions in the version I'm currently running (1.1.2233.0, also latest in Microsoft Store) and the version in the event viewer do not match. Also found the following [events from WindowsUpdateClient](https://github.com/microsoft/terminal/files/5101770/WindowsUpdateClient.zip): > Logged: 19/08/2020 09:24:30 > Installation Started: Windows has started installing the following update: 9N0DX20HK701-Microsoft.WindowsTerminal > Logged: 19/08/2020 09:25:14 > Installation Successful: Windows successfully installed the following update: 9N0DX20HK701-Microsoft.WindowsTerminal There was no system update, but apparently an app update happend sometime around the crash. Looks highly suspicious.
claunia commented 2026-01-31 02:15:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 21, 2020):

We've seen an uptick in these issues very recently--about 7 days since we released the last update. I'm starting to become convinced that this is because of the update (and not the other way around.) Thanks for the info above ^

I had a colleague help me look at dumps from these hangs, and it looks like they happen predominantly when the "do you want to close all tabs?" dialog is open.

Here's my theory:

  1. The store decides there's been an update available for long enough
  2. It asks Terminal to exit nicely
  3. Terminal resists, and says "i've got tabs open -- at least let the user confirm it"
  4. With or without an answer, this looks like Terminal is another intransigent application that needs to be put down, and so it gets terminated and blamed for "hanging".

This is a place where the platform treats us like a "store-managed" application, where we're really not.

I'm tentatively closing this as a /duplicate of #6726. Thanks for following up 😄

@DHowett commented on GitHub (Aug 21, 2020): We've seen an uptick in these issues very recently--about 7 days since we released the last update. I'm starting to become convinced that this _is_ because of the update (and not the other way around.) Thanks for the info above ^ I had a colleague help me look at dumps from these hangs, and it looks like they happen predominantly when the "do you want to close all tabs?" dialog is open. Here's my theory: 1. The store decides there's been an update available for long enough 2. It asks Terminal to exit nicely 3. Terminal resists, and says "i've got tabs open -- at least let the user confirm it" 4. _With or without an answer_, this looks like Terminal is another intransigent application that needs to be put down, and so it gets terminated and _blamed_ for "hanging". This is a place where the platform treats us like a "store-managed" application, where we're really not. I'm tentatively closing this as a /duplicate of #6726. Thanks for following up :smile:
claunia commented 2026-01-31 02:15:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 21, 2020):

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!

@ghost commented on GitHub (Aug 21, 2020): 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!
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 Product-Terminal Resolution-Duplicate 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#10227
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?