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

Startup lag when using a preset to open multiple terminal tabs/panes #17718

New Issue
Open
opened 2026-01-31 05:51:21 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:51:21 +00:00
Owner
Copy Link

Originally created by @CC007 on GitHub (Jun 15, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19044.1706

Other Software

kubectl v1.18.5
WSL (version 2) running Ubuntu (kernel version: 4.19.128)

Steps to reproduce

  1. Setup config file so that WT starts with 2 tabs:

    • first tab contains 5 panes with powershell (1 big on left, 4 vertically small on right)
    • second tab contains 5 panes with bash (1 big on left, 4 vertically small on right)
    • top right pane of powershell runs a kubectl proxy on startup

  2. Open WT

Expected Behavior

It used to open the terminal in less than a second WT to open and for the tabs to be visible, with maybe only the individual panes not being responsive yet until half a second later.

Actual Behavior

Nowadays it takes 3-4 seconds before even the first pane is visible. The pane area is see-through and the top bar is black, rather than white and without any of the tabs showing until after the 3-4 seconds (see image)
afbeelding

What it looks like after it is done loading:
afbeelding

Originally created by @CC007 on GitHub (Jun 15, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 10.0.19044.1706 ### Other Software kubectl v1.18.5 WSL (version 2) running Ubuntu (kernel version: 4.19.128) ### Steps to reproduce 1. Setup config file so that WT starts with 2 tabs: - first tab contains 5 panes with powershell (1 big on left, 4 vertically small on right) - second tab contains 5 panes with bash (1 big on left, 4 vertically small on right) - top right pane of powershell runs a kubectl proxy on startup 2. Open WT ### Expected Behavior It used to open the terminal in less than a second WT to open and for the tabs to be visible, with maybe only the individual panes not being responsive yet until half a second later. ### Actual Behavior Nowadays it takes 3-4 seconds before even the first pane is visible. The pane area is see-through and the top bar is black, rather than white and without any of the tabs showing until after the 3-4 seconds (see image) ![afbeelding](https://user-images.githubusercontent.com/5381337/173827922-939ec9c1-46a1-426e-9428-aa69a29efea8.png) What it looks like after it is done loading: ![afbeelding](https://user-images.githubusercontent.com/5381337/173829520-8ce73e77-66a4-4c3f-913f-4caab363de0b.png)
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:51:21 +00:00
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-Tag-Fix 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#17718
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?