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

Freeze when split panes #23695

New Issue
Closed
opened 2026-01-31 08:49:34 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:49:34 +00:00
Owner
Copy Link

Originally created by @ok3721 on GitHub (Oct 15, 2025).

Windows Terminal version

1.23.12811.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

I use the following command to split current tab into 8 panes

wt -w 0 split-pane -VD `; move-focus previous `; split-pane -HD `; move-focus right `; split-pane -HD `; move-focus first `; split-pane -VD `; move-focus right `; split-pane -VD `; move-focus down `; move-focus left `; split-pane -VD `; move-focus right `; split-pane -VD

Expected Behavior

Current tab is split into 8 panes

Actual Behavior

Terminal app is frozen and not responsive. I also tried use custom actions with the same command, still same result. This behavior is 100% reproducible on a low-spec PC, less frequent on higher end machines. The same command worked fine last month.

Originally created by @ok3721 on GitHub (Oct 15, 2025). ### Windows Terminal version 1.23.12811.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce I use the following command to split current tab into 8 panes ```wt -w 0 split-pane -VD `; move-focus previous `; split-pane -HD `; move-focus right `; split-pane -HD `; move-focus first `; split-pane -VD `; move-focus right `; split-pane -VD `; move-focus down `; move-focus left `; split-pane -VD `; move-focus right `; split-pane -VD``` ### Expected Behavior Current tab is split into 8 panes ### Actual Behavior Terminal app is frozen and not responsive. I also tried use custom actions with the same command, still same result. This behavior is 100% reproducible on a low-spec PC, less frequent on higher end machines. The same command worked fine last month.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:49:35 +00:00
claunia commented 2026-01-31 08:49:37 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 15, 2025):

I indeed can't repro this on my machine (= high end). I did find that the layout isn't always consistent though and sometimes doesn't result in a 4x2 layout.

@lhecker commented on GitHub (Oct 15, 2025): I indeed can't repro this on my machine (= high end). I did find that the layout isn't always consistent though and sometimes doesn't result in a 4x2 layout.
claunia commented 2026-01-31 08:49:37 +00:00
Author
Owner
Copy Link

@ok3721 commented on GitHub (Oct 15, 2025):

I indeed can't repro this on my machine (= high end). I did find that the layout isn't always consistent though and sometimes doesn't result in a 4x2 layout.

I encountered this behavior as well, it is somewhat mitigated by using custom action.

My custom action in JSON setting just in case, it is the same command

    "actions": [
        {
            "command": {
                "action": "multipleActions",
                "actions": [
                    {
                        "action": "splitPane",
                        "split": "vertical",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "previous"
                    },
                    {
                        "action": "splitPane",
                        "split": "horizontal",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "right"
                    },
                    {
                        "action": "splitPane",
                        "split": "horizontal",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "first"
                    },
                    {
                        "action": "splitPane",
                        "split": "vertical",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "right"
                    },
                    {
                        "action": "splitPane",
                        "split": "vertical",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "down"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "left"
                    },
                    {
                        "action": "splitPane",
                        "split": "vertical",
                        "splitMode": "duplicate"
                    },
                    {
                        "action": "moveFocus",
                        "direction": "right"
                    },
                    {
                        "action": "splitPane",
                        "split": "vertical",
                        "splitMode": "duplicate"
                    }
                ]
            },
            "id": "User.multipleActions.D9A430EB",
            "name": "Create My Layout"
        }
    ],
@ok3721 commented on GitHub (Oct 15, 2025): > I indeed can't repro this on my machine (= high end). I did find that the layout isn't always consistent though and sometimes doesn't result in a 4x2 layout. I encountered this behavior as well, it is somewhat mitigated by using custom action. My custom action in JSON setting just in case, it is the same command <details> ```json "actions": [ { "command": { "action": "multipleActions", "actions": [ { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "previous" }, { "action": "splitPane", "split": "horizontal", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "right" }, { "action": "splitPane", "split": "horizontal", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "first" }, { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "right" }, { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "down" }, { "action": "moveFocus", "direction": "left" }, { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" }, { "action": "moveFocus", "direction": "right" }, { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" } ] }, "id": "User.multipleActions.D9A430EB", "name": "Create My Layout" } ], ``` </details>
claunia commented 2026-01-31 08:49:37 +00:00
Author
Owner
Copy Link

@R3DW1N3 commented on GitHub (Oct 16, 2025):

I have this issue as well. Seems like there is a soft limit to the number of panes you can split at once from the command line. For me, the crash happens around the 6th or 7th split. Splitting into different profiles, as well. This was not happening a couple of days ago, so it seems like a bug with the latest release.

@R3DW1N3 commented on GitHub (Oct 16, 2025): I have this issue as well. Seems like there is a soft limit to the number of panes you can split at once from the command line. For me, the crash happens around the 6th or 7th split. Splitting into different profiles, as well. This was not happening a couple of days ago, so it seems like a bug with the latest release.
claunia commented 2026-01-31 08:49:38 +00:00
Author
Owner
Copy Link

@avenmore commented on GitHub (Oct 17, 2025):

Added metoo to #19467.

@avenmore commented on GitHub (Oct 17, 2025): Added metoo to #19467.
claunia commented 2026-01-31 08:49:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 22, 2025):

Thanks all - it looks like this is a duplicate of #19467, which has the honor of having been triaged first ;P

@DHowett commented on GitHub (Oct 22, 2025): Thanks all - it looks like this is a duplicate of #19467, which has the honor of having been triaged first ;P
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 Needs-Triage
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#23695
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?