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

Windows Terminal crashing when resizing panes #11436

New Issue
Closed
opened 2026-01-31 02:47:34 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 02:47:34 +00:00
Owner
Copy Link

Originally created by @wolffberg on GitHub (Nov 16, 2020).

Environment

Windows build number....: 10.0.19041.0 (issue also seen on earlier versions)
Windows Terminal version: 1.4.3141.0
Pwsh version............: 7.1.0        (issue also seen on earlier versions)

Steps to reproduce

  • Open Windows Terminal
  • Maximize window to have more space for resizing (optional but makes it easier to reproduce)
  • Split the terminal horizontally and then vertically into panes
  • Resize bottom two panes up and down repeatedly using keyboard shortcuts

Expected behavior

The panes should resize without issues

Actual behavior

Windows Terminal crashes

Notes

  • The crash can happen at any given time while resizing panes. Some times you will be able to resize a lot, some times the crash happens instantly.
  • The issue have been observed on multiple different devices.
  • The issue is tested with pwsh, wsl and cmd running in the panes.
Originally created by @wolffberg on GitHub (Nov 16, 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 (issue also seen on earlier versions) Windows Terminal version: 1.4.3141.0 Pwsh version............: 7.1.0 (issue also seen on earlier versions) ``` # Steps to reproduce - Open Windows Terminal - Maximize window to have more space for resizing (optional but makes it easier to reproduce) - Split the terminal horizontally and then vertically into panes - Resize bottom two panes up and down repeatedly using keyboard shortcuts # Expected behavior The panes should resize without issues # Actual behavior Windows Terminal crashes # Notes - The crash can happen at any given time while resizing panes. Some times you will be able to resize a lot, some times the crash happens instantly. - The issue have been observed on multiple different devices. - The issue is tested with `pwsh`, `wsl` and `cmd` running in the panes.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Author-FeedbackSeverity-Crash labels 2026-01-31 02:47:34 +00:00
claunia commented 2026-01-31 02:47:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 20, 2020):

That's almost certainly not right. Would you mind filling out a feedback item to see if we can get some crash logs?

If that doesn't work, I'll write up tracing steps. 😄

@DHowett commented on GitHub (Nov 20, 2020): That's almost certainly not right. Would you mind filling out a feedback item to see if we can get some crash logs? If that doesn't work, I'll write up tracing steps. :smile:
claunia commented 2026-01-31 02:47:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 20, 2020):

/feedback

@DHowett commented on GitHub (Nov 20, 2020): /feedback
claunia commented 2026-01-31 02:47:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 20, 2020):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Nov 20, 2020): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 02:47:36 +00:00
Author
Owner
Copy Link

@wolffberg commented on GitHub (Nov 23, 2020):

Sure thing https://aka.ms/AAae833 🤞

@wolffberg commented on GitHub (Nov 23, 2020): Sure thing https://aka.ms/AAae833 🤞
claunia commented 2026-01-31 02:47:37 +00:00
Author
Owner
Copy Link

@webnoob commented on GitHub (Nov 24, 2020):

I too have a similar issue. I have a powershell script which loads scripts into 2 tabs with 1 pane on one tab and 5 panes on the other. When it's loading, if I grab the bottom right corner of the terminal and drag it quickly to resize, it closes the terminal.

This is the command I use (specific to my project but the general idea should help):

wt `; new-tab -p "DevTestingApi" powershell.exe -command "yarn start:testing" `; new-tab -p "DevApi" powershell.exe -command "yarn start:dev" `; split-pane -p "DevApp" powershell.exe -command "yarn dev" `; split-pane -p "DevCommon" powershell.exe -command "yarn dev" `; split-pane -p "DevApp" powershell.exe -command "yarn test:e2e" `; split-pane -p "DevApp" powershell.exe -command "yarn test:unit:ui"
@webnoob commented on GitHub (Nov 24, 2020): I too have a similar issue. I have a powershell script which loads scripts into 2 tabs with 1 pane on one tab and 5 panes on the other. When it's loading, if I grab the bottom right corner of the terminal and drag it quickly to resize, it closes the terminal. This is the command I use (specific to my project but the general idea should help): ``` wt `; new-tab -p "DevTestingApi" powershell.exe -command "yarn start:testing" `; new-tab -p "DevApi" powershell.exe -command "yarn start:dev" `; split-pane -p "DevApp" powershell.exe -command "yarn dev" `; split-pane -p "DevCommon" powershell.exe -command "yarn dev" `; split-pane -p "DevApp" powershell.exe -command "yarn test:e2e" `; split-pane -p "DevApp" powershell.exe -command "yarn test:unit:ui" ```
claunia commented 2026-01-31 02:47:37 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 25, 2020):

Alright, this is gonna seem like I'm giving you the runaround. Sorry for that.

On Monday, I set up better tracing for our feedback hub entry! Unfortunately, it requires a "repro mode" feedback hub capture.

Would you mind filing another feedback hub item? It'll help us capture those new traces.
Please make sure you do the following:

  1. Use the Apps, "Windows Terminal" category. There shouldn't be a "(Preview)" version any more.
    • This is what enables the terminal-specific tracing
  2. Use "start recording" .. you can choose "include data about ... general". image
  3. Crash Terminal while it's recording!
  4. Stop recording, submit, share link like before.

Thanks again 😄

@DHowett commented on GitHub (Nov 25, 2020): Alright, this is gonna seem like I'm giving you the runaround. Sorry for that. On Monday, I set up better tracing for our feedback hub entry! Unfortunately, it requires a "repro mode" feedback hub capture. Would you mind filing another feedback hub item? It'll help us capture those new traces. Please make sure you do the following: 1. Use the Apps, "Windows Terminal" category. There shouldn't be a "(Preview)" version any more. * This is what enables the terminal-specific tracing 2. Use "start recording" .. you can choose "include data about ... general". ![image](https://user-images.githubusercontent.com/189190/100270447-f3b88000-2f0c-11eb-8444-3c4d98170d8d.png) 3. Crash Terminal while it's recording! 4. Stop recording, submit, share link like before. Thanks again :smile:
claunia commented 2026-01-31 02:47:37 +00:00
Author
Owner
Copy Link

@wolffberg commented on GitHub (Nov 26, 2020):

There you go https://aka.ms/AAaetoj

Yesterday I tried replicating the issue on a fresh Windows 10 installation and weren't able to reproduce. I only added my keybindings to settings.json but didn't install any fonts. I usually use https://github.com/powerline/fonts 🤔

        {
            "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
            "hidden": false,
            "name": "PowerShell Core",
            "source": "Windows.Terminal.PowershellCore",
            "fontFace": "Meslo LG S DZ for Powerline",
            "fontSize": 10
        },
@wolffberg commented on GitHub (Nov 26, 2020): There you go https://aka.ms/AAaetoj Yesterday I tried replicating the issue on a fresh Windows 10 installation and weren't able to reproduce. I only added my keybindings to `settings.json` but didn't install any fonts. I usually use https://github.com/powerline/fonts 🤔 ``` { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell Core", "source": "Windows.Terminal.PowershellCore", "fontFace": "Meslo LG S DZ for Powerline", "fontSize": 10 }, ```
claunia commented 2026-01-31 02:47:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 26, 2021):

Oh no, with the holidays at the end of the year, it looks like this one got lost. Now that it's been more than 60 days, the feedback got flushed from the backend ☹️

Would you mind submitting it again? I'm fairly confident that this is the same issue as #4907, but it'll be good to know for sure.

Sorry about that!

@zadjii-msft commented on GitHub (Mar 26, 2021): Oh no, with the holidays at the end of the year, it looks like this one got lost. Now that it's been more than 60 days, the feedback got flushed from the backend ☹️ Would you mind submitting it again? I'm fairly confident that this is the same issue as #4907, but it'll be good to know for sure. Sorry about that!
claunia commented 2026-01-31 02:47:38 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 30, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 30, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 02:47:38 +00:00
Author
Owner
Copy Link

@VanVan commented on GitHub (Oct 19, 2022):

I have the same problem, I will open a new thread

@VanVan commented on GitHub (Oct 19, 2022): I have the same problem, I will open a new thread
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-Author-Feedback Needs-Tag-Fix Needs-Triage 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#11436
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?