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 crashes when second-last tab is closed and alwaysShowTabs is false #5113

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

Originally created by @TBBle on GitHub (Nov 21, 2019).

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

1 Set the following global settings in profile.json

    "alwaysShowTabs": false,
    "showTabsInTitlebar": false,

2 Start Terminal

  • No tab bar visible

3 Control-Shift-t to create a new tab

  • Here it's PowerShell Core, but reproduces with git-bash for example
  • Tab bar becomes visible here.
  • Switching between tabs here does not affect the outcome.

4 Type exit to terminate the currently-visible shell

  • Middle-clicking the active tab also works. Middle-clicking the other tab does not reproduce.
  • If extra shells were opened, this doesn't reproduce, it seems to only happen when the tab bar is hidden as part of closing the current tab.
  • Setting close-on-exit means this doesn't reproduce until the tab is closed, so not related to the shell process terminating.

Expected behavior

  • Current tab closes
  • Tab bar disappears
  • Other tab is usable.

Actual behavior

  • Current tab closes
  • Tab bar disappears
  • (!!) Other tab content is visible, but cursor is not flashing and input is not handled
  • (!!) A few seconds later, the application crashes, logged in Event Viewer:
Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: TerminalControl.dll, version: 1.0.1910.22001, time stamp: 0x5daf7988
Exception code: 0xc0000005
Fault offset: 0x0000000000008268
Faulting process ID: 0x2bec
Faulting application start time: 0x01d5a030043b34f4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\TerminalControl.dll
Report ID: eb98c87f-b71c-4108-97b3-626d6a0af7f1
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I have raised a Feedback Hub issue, but it has not yet appeared in "My feedback". I'll update this ticket once it's showing up (it said it would take a few minutes, but now it shows nothing...)

Originally created by @TBBle on GitHub (Nov 21, 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. 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 NT 10.0.18362.0 Windows Terminal version (if applicable): 0.6.2951.0 Any other software? ``` # Steps to reproduce 1 Set the following global settings in profile.json ```json "alwaysShowTabs": false, "showTabsInTitlebar": false, ``` 2 Start Terminal * No tab bar visible 3 _Control-Shift-t_ to create a new tab * Here it's PowerShell Core, but reproduces with git-bash for example * Tab bar becomes visible here. * Switching between tabs here does not affect the outcome. 4 Type `exit` to terminate the currently-visible shell * Middle-clicking the active tab also works. Middle-clicking the *other* tab does not reproduce. * If extra shells were opened, this doesn't reproduce, it seems to only happen when the tab bar is hidden as part of closing the current tab. * Setting close-on-exit means this doesn't reproduce until the tab is closed, so not related to the shell process terminating. # Expected behavior * Current tab closes * Tab bar disappears * Other tab is usable. # Actual behavior * Current tab closes * Tab bar disappears * (!!) Other tab content is visible, but cursor is not flashing and input is not handled * (!!) A few seconds later, the application crashes, logged in Event Viewer: ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2 Faulting module name: TerminalControl.dll, version: 1.0.1910.22001, time stamp: 0x5daf7988 Exception code: 0xc0000005 Fault offset: 0x0000000000008268 Faulting process ID: 0x2bec Faulting application start time: 0x01d5a030043b34f4 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\TerminalControl.dll Report ID: eb98c87f-b71c-4108-97b3-626d6a0af7f1 Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` I have raised a Feedback Hub issue, but it has not yet appeared in "My feedback". I'll update this ticket once it's showing up (it said it would take a few minutes, but now it shows nothing...)
claunia added the Resolution-Duplicate label 2026-01-31 00:05:22 +00:00
claunia commented 2026-01-31 00:05:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 21, 2019):

I'm marking this one for feedback until we get that link. Thanks!

@DHowett-MSFT commented on GitHub (Nov 21, 2019): I'm marking this one for feedback until we get that link. Thanks!
claunia commented 2026-01-31 00:05:23 +00:00
Author
Owner
Copy Link

@TBBle commented on GitHub (Nov 22, 2019):

My original feedback never appeared, so I recreated it on another machine: https://aka.ms/AA6p585

Here is the Application Error in Event Viewer. It looks the same as the one from my other machine

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: TerminalControl.dll, version: 1.0.1910.22001, time stamp: 0x5daf7988
Exception code: 0xc0000005
Fault offset: 0x0000000000008268
Faulting process ID: 0x4144
Faulting application start time: 0x01d5a0f636dc63b3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\TerminalControl.dll
Report ID: af74987f-91be-4e0f-913b-8fa7701c124e
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@TBBle commented on GitHub (Nov 22, 2019): My original feedback never appeared, so I recreated it on another machine: https://aka.ms/AA6p585 Here is the Application Error in Event Viewer. It looks the same as the one from my other machine ``` Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2 Faulting module name: TerminalControl.dll, version: 1.0.1910.22001, time stamp: 0x5daf7988 Exception code: 0xc0000005 Fault offset: 0x0000000000008268 Faulting process ID: 0x4144 Faulting application start time: 0x01d5a0f636dc63b3 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\TerminalControl.dll Report ID: af74987f-91be-4e0f-913b-8fa7701c124e Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ```
claunia commented 2026-01-31 00:05:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 25, 2019):

Based on the signature, this looks like a /dupe of #2947. Thanks for the report!

@DHowett-MSFT commented on GitHub (Nov 25, 2019): Based on the signature, this looks like a /dupe of #2947. Thanks for the report!
claunia commented 2026-01-31 00:05:24 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 25, 2019):

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 (Nov 25, 2019): 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 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#5113
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?