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

Windows Terminal Preview consistently crashes when closing panes in certain layouts #21804

New Issue
Closed
opened 2026-01-31 07:55:20 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:55:20 +00:00
Owner
Copy Link

Originally created by @itszn on GitHub (Jun 2, 2024).

Windows Terminal version

1.21.1272.0

Windows build number

Microsoft Windows [Version 10.0.22631.3672]

Other Software

> wsl --version
WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3672

> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)

OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f 31 Mar 2020 running inside WSL connecting to my host

Steps to reproduce

Crash report:
https://aka.ms/AAqonu3

Reproduce

Open a new fresh terminal session. Then split once vertically. Then split the new pane vertically again. Now the middle pane will crash when closed and crash the whole terminal.

https://github.com/microsoft/terminal/assets/1857794/a7500464-875b-4584-a55c-cdf4d9cfa597

My Experience With The Bug

Very often, when using the terminal, I end up with several terminal panes which are in this state, such that when they are closed they crash the entire terminal.

This seems to only happen when they are in certain positions, ie have a pane on either side, and if I close the ones around it, it often fixes itself.

In this video I am showing how exiting specific panes will crash the terminal, while exiting the other panes does not crash it.

I also show how closing enough of the other panes fixes the issue, and also moving the pane to a new tab fixes the issue (for that single pane).

https://github.com/microsoft/terminal/assets/1857794/de269f33-e399-4ae3-a6f3-943fb8ebafe6

Also bc the state of the panes is saved on close, when I reopen the terminal, it reloads the last save (which was last time it closed cleanly). This ends up opening a new pane in the same positions as the old ones, and once again the same pane position ends up in this crashing state every single time.

Expected Behavior

I expect that the whole terminal doesn't crash when I close a single pane.

Actual Behavior

The whole terminal crashes when I close these specific panes.

Originally created by @itszn on GitHub (Jun 2, 2024). ### Windows Terminal version 1.21.1272.0 ### Windows build number Microsoft Windows [Version 10.0.22631.3672] ### Other Software ``` > wsl --version WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3672 > wsl --list Windows Subsystem for Linux Distributions: Ubuntu-20.04 (Default) ``` `OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f 31 Mar 2020` running inside WSL connecting to my host ### Steps to reproduce Crash report: https://aka.ms/AAqonu3 # Reproduce Open a new fresh terminal session. Then split once vertically. Then split the new pane vertically again. Now the middle pane will crash when closed and crash the whole terminal. https://github.com/microsoft/terminal/assets/1857794/a7500464-875b-4584-a55c-cdf4d9cfa597 # My Experience With The Bug Very often, when using the terminal, I end up with several terminal panes which are in this state, such that when they are closed they crash the entire terminal. This seems to only happen when they are in certain positions, ie have a pane on either side, and if I close the ones around it, it often fixes itself. In this video I am showing how exiting specific panes will crash the terminal, while exiting the other panes does not crash it. I also show how closing enough of the other panes fixes the issue, and also moving the pane to a new tab fixes the issue (for that single pane). https://github.com/microsoft/terminal/assets/1857794/de269f33-e399-4ae3-a6f3-943fb8ebafe6 Also bc the state of the panes is saved on close, when I reopen the terminal, it reloads the last save (which was last time it closed cleanly). This ends up opening a new pane in the same positions as the old ones, and once again the same pane position ends up in this crashing state every single time. ### Expected Behavior I expect that the whole terminal doesn't crash when I close a single pane. ### Actual Behavior The whole terminal crashes when I close these specific panes.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:55:20 +00:00
claunia commented 2026-01-31 07:55:21 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 2, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Jun 2, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Windows Terminal crashing when resizing panes (#8287)](https://github.com/microsoft/terminal/issues/8287), similarity score: 0.82 - [Terminal crashes after splitting panes - all profiles, orientations affected (#15431)](https://github.com/microsoft/terminal/issues/15431), similarity score: 0.81 - [Windows Terminal crashing when resizing panes (#14254)](https://github.com/microsoft/terminal/issues/14254), similarity score: 0.80 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:55:22 +00:00
Author
Owner
Copy Link

@brookst commented on GitHub (Jun 3, 2024):

Can confirm, closing the middle split:

Faulting application name: WindowsTerminal.exe, version: 1.21.2405.6002, time stamp: 0x66396ac3
Faulting module name: TerminalApp.dll, version: 1.21.2405.6002, time stamp: 0x66396a58
Exception code: 0xc0000005
Fault offset: 0x0000000000010f54
Faulting process ID: 0x0x52A0
Faulting application start time: 0x0x1DAB549726C9AFD
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe\TerminalApp.dll
Report ID: 7f826e57-c0ad-4dd5-9f5f-46d62706697e
Faulting package full name: Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Bucket ID: 6f6826e3bae54d4d9e605254efe4edfc (2188839943657549308)

@brookst commented on GitHub (Jun 3, 2024): Can confirm, closing the middle split: > Faulting application name: WindowsTerminal.exe, version: 1.21.2405.6002, time stamp: 0x66396ac3 > Faulting module name: TerminalApp.dll, version: 1.21.2405.6002, time stamp: 0x66396a58 > Exception code: 0xc0000005 > Fault offset: 0x0000000000010f54 > Faulting process ID: 0x0x52A0 > Faulting application start time: 0x0x1DAB549726C9AFD > Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe\TerminalApp.dll > Report ID: 7f826e57-c0ad-4dd5-9f5f-46d62706697e > Faulting package full name: Microsoft.WindowsTerminalPreview_1.21.1272.0_x64__8wekyb3d8bbwe > Faulting package-relative application ID: App > Bucket ID: 6f6826e3bae54d4d9e605254efe4edfc (2188839943657549308)
claunia commented 2026-01-31 07:55:22 +00:00
Author
Owner
Copy Link

@TGThorax commented on GitHub (Jun 5, 2024):

Same with newer version (About page says 1.21.1382.0):

Faulting application name: WindowsTerminal.exe, version: 1.21.2405.17002, time stamp: 0x66479c70
Faulting module name: TerminalApp.dll, version: 1.21.2405.17002, time stamp: 0x66479c03
Exception code: 0xc0000005
Fault offset: 0x0000000000010f54
Faulting process id: 0x0x65F0
Faulting application start time: 0x0x1DAB720B652D59B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe\TerminalApp.dll
Report Id: a9475c0d-472f-4556-8868-9670850e4e8f
Faulting package full name: Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

@TGThorax commented on GitHub (Jun 5, 2024): Same with newer version (About page says 1.21.1382.0): > Faulting application name: WindowsTerminal.exe, version: 1.21.2405.17002, time stamp: 0x66479c70 Faulting module name: TerminalApp.dll, version: 1.21.2405.17002, time stamp: 0x66479c03 Exception code: 0xc0000005 Fault offset: 0x0000000000010f54 Faulting process id: 0x0x65F0 Faulting application start time: 0x0x1DAB720B652D59B Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe\TerminalApp.dll Report Id: a9475c0d-472f-4556-8868-9670850e4e8f Faulting package full name: Microsoft.WindowsTerminalPreview_1.21.1382.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
claunia commented 2026-01-31 07:55:22 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 5, 2024):

I'm fairly certain that this is a duplicate of #17305. That user also reported that opening 3 panes and closing the middle one crashes the application. It was recently fixed in the Canary build.
(However, it also caused a regression unfortunately. That one was also fixed recently, but it'll probably take a few more hours until that's in the Canary build too.)

@lhecker commented on GitHub (Jun 5, 2024): I'm fairly certain that this is a duplicate of #17305. That user also reported that opening 3 panes and closing the middle one crashes the application. It was recently fixed in the Canary build. (However, it also caused a regression unfortunately. That one was also fixed recently, but it'll probably take a few more hours until that's in the Canary build too.)
claunia commented 2026-01-31 07:55:22 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 10, 2024):

Thanks for filing! Closing as a /dup of #17305.

@carlos-zamora commented on GitHub (Jul 10, 2024): Thanks for filing! Closing as a /dup of #17305.
claunia commented 2026-01-31 07:55:22 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 10, 2024):

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 (Jul 10, 2024): 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#21804
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?