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

Tab switch looks slow? #12370

New Issue
Closed
opened 2026-01-31 03:13:46 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 03:13:46 +00:00
Owner
Copy Link

Originally created by @ThomsonTan on GitHub (Feb 2, 2021).

Environment

Windows build number: 10.0.19042.746
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Press ctrl+tab to switch tabs, it shows a drop list of tabs, then switch to the next tab.

Expected behavior

The switch should be down immediately if I press ctrl+tab and release the keys immediately.

Actual behavior

But it seems taking almost 1 sec to complete the switch, this sluggish could be very annoy if I want to switch to the next tab for some peeking and switch back.

Originally created by @ThomsonTan on GitHub (Feb 2, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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.19042.746 Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce Press ctrl+tab to switch tabs, it shows a drop list of tabs, then switch to the next tab. <!-- A description of how to trigger this bug. --> # Expected behavior The switch should be down immediately if I press ctrl+tab and release the keys immediately. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior But it seems taking almost 1 sec to complete the switch, this sluggish could be very annoy if I want to switch to the next tab for some peeking and switch back. <!-- What's actually happening? -->
claunia commented 2026-01-31 03:13:47 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Feb 2, 2021):

@ThomsonTan

  1. What version of terminal are you using?
  2. Does the sluggishness start immediately or after running the Terminal for a while?
  3. How many tabs are open?
@Don-Vito commented on GitHub (Feb 2, 2021): @ThomsonTan 1. What version of terminal are you using? 2. Does the sluggishness start immediately or after running the Terminal for a while? 3. How many tabs are open?
claunia commented 2026-01-31 03:13:47 +00:00
Author
Owner
Copy Link

@ThomsonTan commented on GitHub (Feb 2, 2021):

  1. The version string is Microsoft.WindowsTerminalPreview_1.4.2652.0_x64.
  2. I am not sure it start immediately after launch. I just tried launching a separate instance of wt.exe, also with 4 tabs, seems the switching if very fluent.
  3. 4 tabs, starts from powershell, but I launched python under cmd.exe within the powershell tab.
@ThomsonTan commented on GitHub (Feb 2, 2021): 1. The version string is Microsoft.WindowsTerminalPreview_1.4.2652.0_x64. 2. I am not sure it start immediately after launch. I just tried launching a separate instance of wt.exe, also with 4 tabs, seems the switching if very fluent. 3. 4 tabs, starts from powershell, but I launched python under cmd.exe within the powershell tab.
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Feb 2, 2021):

Asking this because there are several very similar discussions, around tab switching and drop-down menu becoming sluggish after some time: https://github.com/microsoft/terminal/issues/7710 (and https://github.com/microsoft/terminal/issues/8702 that was closed as duplicate)

@Don-Vito commented on GitHub (Feb 2, 2021): Asking this because there are several very similar discussions, around tab switching and drop-down menu becoming sluggish after some time: https://github.com/microsoft/terminal/issues/7710 (and https://github.com/microsoft/terminal/issues/8702 that was closed as duplicate)
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Feb 2, 2021):

Also in 1.4 there was some slowness that was related to the amount of tabs (solved in 1.5) but it might be irrelevant if it happens to you with a small amount of tabs as well.

@Don-Vito commented on GitHub (Feb 2, 2021): Also in 1.4 there was some slowness that was related to the amount of tabs (solved in 1.5) but it might be irrelevant if it happens to you with a small amount of tabs as well.
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Feb 3, 2021):

@ThomsonTan have you tried uninstalling Powershell 64 bit and installing Powershell 32 bit (e.g. from https://github.com/PowerShell/PowerShell/releases > Some release > Assests > PowerShell-7.1.1-win-x86.msi)?

@JohnLukeBentley commented on GitHub (Feb 3, 2021): @ThomsonTan have you tried uninstalling Powershell 64 bit and installing Powershell 32 bit (e.g. from https://github.com/PowerShell/PowerShell/releases > Some release > Assests > PowerShell-7.1.1-win-x86.msi)?
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@ThomsonTan commented on GitHub (Feb 3, 2021):

@JohnLukeBentley I haven't tried 32-bit installer. I'd prefer 64-bit in general, but I could try that if it could help gather data for locating the problem.

@ThomsonTan commented on GitHub (Feb 3, 2021): @JohnLukeBentley I haven't tried 32-bit installer. I'd prefer 64-bit in general, but I could try that if it could help gather data for locating the problem.
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@JohnLukeBentley commented on GitHub (Feb 3, 2021):

That solved the problem for me (over in #7710 and #3515). And so yes, that would help with locating the problem(s).

@JohnLukeBentley commented on GitHub (Feb 3, 2021): That solved the problem for me (over in #7710 and #3515). And so yes, that would help with locating the problem(s).
claunia commented 2026-01-31 03:13:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 3, 2021):

Alright, hopefully it does help. Otherwise, I'd suggest updating the Terminal - preview just got updated to 1.6 a week ago, so it's very possible that this was fixed sometime in the last two releases

@zadjii-msft commented on GitHub (Feb 3, 2021): Alright, hopefully it does help. Otherwise, I'd suggest updating the Terminal - preview just got updated to 1.6 a week ago, so it's _very possible_ that this was fixed sometime in the last two releases
claunia commented 2026-01-31 03:13:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 7, 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 (Feb 7, 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 03:13:49 +00:00
Author
Owner
Copy Link

@guillebot commented on GitHub (Feb 9, 2021):

I have the same problem. Extremely slow switching tabs either via ctrl+tab or mouse click.

@guillebot commented on GitHub (Feb 9, 2021): I have the same problem. Extremely slow switching tabs either via ctrl+tab or mouse click.
claunia commented 2026-01-31 03:13:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 10, 2021):

You know what, this seems to be happening to me too (on preview 1.6.10272.0). I thought it was just my slaptop chugging because I was building at first, but now I don't think there's anything else running that should cause such a delay.

Weirdly though, it doesn't happen on fresh terminal windows. It's only happening on my primary on that I've been using for a few days. There's nothing weird about it in Task Manager - CPU, memory, GPU all look like they're in reasonable limits. But tab switching (via clicking AND via the ATS), tab creating, pane splitting are all laggy. The command palette takes a while to appear, and long to repopulate when starting to type in it. Heck, even just navigating the new tab dropdown with the arrow keys seems particularly un-responsive.

I'll keep my eye on this one. Maybe over the course of 1.7 we'll have a better idea of what's going on. Maybe I'll get a consistent repro. If anyone has any thoughts, or wants to profile their terminal and figure it out, I'm all ears.

@zadjii-msft commented on GitHub (Feb 10, 2021): You know what, this seems to be happening to me too (on preview 1.6.10272.0). I thought it was just my slaptop chugging because I was building at first, but now I don't think there's anything else running that should cause such a delay. Weirdly though, it doesn't happen on fresh terminal windows. It's only happening on my primary on that I've been using for a few days. There's nothing weird about it in Task Manager - CPU, memory, GPU all look like they're in reasonable limits. But tab switching (via clicking AND via the ATS), tab creating, pane splitting are all laggy. The command palette takes a while to appear, and long to repopulate when starting to type in it. Heck, even just navigating the new tab dropdown with the arrow keys seems particularly un-responsive. I'll keep my eye on this one. Maybe over the course of 1.7 we'll have a better idea of what's going on. Maybe I'll get a consistent repro. If anyone has any thoughts, or wants to profile their terminal and figure it out, I'm all ears.
claunia commented 2026-01-31 03:13:49 +00:00
Author
Owner
Copy Link

@guillebot commented on GitHub (Feb 10, 2021):

You know what, this seems to be happening to me too (on preview 1.6.10272.0). I thought it was just my slaptop chugging because I was building at first, but now I don't think there's anything else running that should cause such a delay.

Weirdly though, it doesn't happen on fresh terminal windows. It's only happening on my primary on that I've been using for a few days. There's nothing weird about it in Task Manager - CPU, memory, GPU all look like they're in reasonable limits. But tab switching (via clicking AND via the ATS), tab creating, pane splitting are all laggy. The command palette takes a while to appear, and long to repopulate when starting to type in it. Heck, even just navigating the new tab dropdown with the arrow keys seems particularly un-responsive.

I'll keep my eye on this one. Maybe over the course of 1.7 we'll have a better idea of what's going on. Maybe I'll get a consistent repro. If anyone has any thoughts, or wants to profile their terminal and figure it out, I'm all ears.

My PC is quite powerfull, its an i9-10900 with 64GB RAM and NVME disks. Everything seems to fly but this terminal. There is definitely some problem here.

It's a shame because it is the best terminal I've ever tried for windows, it replicates a lot of nice features I'm used to use in the *nix world.

@guillebot commented on GitHub (Feb 10, 2021): > You know what, this seems to be happening to me too (on preview 1.6.10272.0). I thought it was just my slaptop chugging because I was building at first, but now I don't think there's anything else running that should cause such a delay. > > Weirdly though, it doesn't happen on fresh terminal windows. It's only happening on my primary on that I've been using for a few days. There's nothing weird about it in Task Manager - CPU, memory, GPU all look like they're in reasonable limits. But tab switching (via clicking AND via the ATS), tab creating, pane splitting are all laggy. The command palette takes a while to appear, and long to repopulate when starting to type in it. Heck, even just navigating the new tab dropdown with the arrow keys seems particularly un-responsive. > > I'll keep my eye on this one. Maybe over the course of 1.7 we'll have a better idea of what's going on. Maybe I'll get a consistent repro. If anyone has any thoughts, or wants to profile their terminal and figure it out, I'm all ears. My PC is quite powerfull, its an i9-10900 with 64GB RAM and NVME disks. Everything seems to fly but this terminal. There is definitely some problem here. It's a shame because it is the best terminal I've ever tried for windows, it replicates a lot of nice features I'm used to use in the *nix world.
claunia commented 2026-01-31 03:13:50 +00:00
Author
Owner
Copy Link

@guillebot commented on GitHub (Feb 10, 2021):

Preview seems to do much better!

@guillebot commented on GitHub (Feb 10, 2021): Preview seems to do much better!
claunia commented 2026-01-31 03:13:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 25, 2021):

You know what, in retrospect, this seems similar enough to #7710 that I'm gonna close this as a dupe to try and keep the discussion contained. Thanks!

/dup #7710

@zadjii-msft commented on GitHub (Feb 25, 2021): You know what, in retrospect, this seems similar enough to #7710 that I'm gonna close this as a dupe to try and keep the discussion contained. Thanks! /dup #7710
claunia commented 2026-01-31 03:13:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 25, 2021):

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 (Feb 25, 2021): 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 Area-Performance Help Wanted Issue-Bug Product-Terminal 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#12370
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?