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

Bug Report: closing powershell tab (multiple opened) hangs the application #2208

New Issue
Closed
opened 2026-01-30 22:49:34 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:49:34 +00:00
Owner
Copy Link

Originally created by @miaouPlop on GitHub (Jun 25, 2019).

Environment

Windows build number:  Microsoft Windows [version 10.0.18362.30]
Windows Terminal version (if applicable): preview (from the Store)

Steps to reproduce

Launch the application. You have at least one tab. Now, open a new tab (any console type) and then close the first one (either by clicking the "close" button or by using the keyboard shortcut (mine is bind to ctrl+shift+w) or wheel-clicking).

Expected behavior

The tab should close fine and not block the entire application.
It should be noted that the first tab closes normally if you type "exit" (and chose to "closeonexit").

Actual behavior

The entire WindowsTerminal application is blocked and we have to close it with the processus manager.

This bug might be related to #1575, #1585, #1588 and #1530.

Originally created by @miaouPlop on GitHub (Jun 25, 2019). <!-- 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. 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.18362.30] Windows Terminal version (if applicable): preview (from the Store) ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Launch the application. You have at least one tab. Now, open a new tab (any console type) and then close the first one (either by clicking the "close" button or by using the keyboard shortcut (mine is bind to ctrl+shift+w) or wheel-clicking). # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The tab should close fine and not block the entire application. It should be noted that the first tab closes normally if you type "exit" (and chose to "closeonexit"). # Actual behavior <!-- What's actually happening? --> The entire WindowsTerminal application is blocked and we have to close it with the processus manager. This bug might be related to #1575, #1585, #1588 and #1530.
claunia added the Needs-TriageNeeds-Tag-FixResolution-Duplicate labels 2026-01-30 22:49:34 +00:00
claunia commented 2026-01-30 22:49:35 +00:00
Author
Owner
Copy Link

@miaouPlop commented on GitHub (Jun 25, 2019):

After some more testing it appears more convoluted than that. The crash only happens when trying to close a powershell console so #1530 seems really connected to that bug.

If I try to close any tab when I have three, the application hangs. 
If I try to close the last tab (when I have >= 3 tabs) then, the application hangs. 
If I now close a tab that is neither the first one nor the last one when I have >= 4 tabs, then it somehow "repairs" the index (to a certain extent) and I can close tabs rather randomly.

I can also reference this PR #892 that ended up by the fix microsoft/microsoft-ui-xaml#629.

@miaouPlop commented on GitHub (Jun 25, 2019): After some more testing it appears more convoluted than that. The crash only happens when trying to close a powershell console so #1530 seems really connected to that bug. ```none If I try to close any tab when I have three, the application hangs. If I try to close the last tab (when I have >= 3 tabs) then, the application hangs. If I now close a tab that is neither the first one nor the last one when I have >= 4 tabs, then it somehow "repairs" the index (to a certain extent) and I can close tabs rather randomly. ``` I can also reference this PR #892 that ended up by the fix [microsoft/microsoft-ui-xaml#629](https://github.com/microsoft/microsoft-ui-xaml/pull/629).
claunia commented 2026-01-30 22:49:35 +00:00
Author
Owner
Copy Link

@JacomusP commented on GitHub (Jun 27, 2019):

I was just about to open a new issue but I'm glad I found this one. Just wanted to say that I'm also experiencing this issue of closing the powershell tab that is opened by default.

@JacomusP commented on GitHub (Jun 27, 2019): I was just about to open a new issue but I'm glad I found this one. Just wanted to say that I'm also experiencing this issue of closing the powershell tab that is opened by default.
claunia commented 2026-01-30 22:49:36 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

Probably #1445.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): Probably #1445.
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 Needs-Tag-Fix Needs-Triage 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#2208
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?