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

Tabs Become Irresponsive After Long Use #11960

New Issue
Closed
opened 2026-01-31 03:02:28 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 03:02:28 +00:00
Owner
Copy Link

Originally created by @yakobyd on GitHub (Jan 4, 2021).

Environment

Microsoft Windows [Version 10.0.19041.685]
Windows Terminal Version: 1.4.3243.0

Steps to reproduce

Issue: The terminal becomes irresponsive after few days of use. Specifically, switching tabs is very slow.

I often leave my terminal app open for a week of continuous use. Usually, after three days, the terminal becomes very slow to interact with. This has been happening consistently for the past month. Namely, I have experienced this issue at least four times by now.

To reproduce, open the terminal and use it for three days without closing the app. The terminal should become very slow at this point. If one closes the terminal and reopens it, it becomes responsive again.

Additional functionalities that become slower:

  • Typing.
  • Opening new tabs and closing existing tabs.

I have not included these functionalities in the videos below as they are slightly harder to notice.

Expected behavior

Below is the behavior of a freshly opened terminal. Note that tab switching is immediate after each click.

https://user-images.githubusercontent.com/39068219/103559013-26677800-4ebe-11eb-89fd-c4545bd07f5e.mp4

Actual behavior

Below is the behavior of a terminal that was used for three days (I have cleared all output). Note that after clicking, tab switching is very slow. Clicks are not apparent in this video, but I tried to click as soon as the mouse hovers over the tab. Hopefully, the difference is clear when comparing with the expected behavior above.

https://user-images.githubusercontent.com/39068219/103559035-2cf5ef80-4ebe-11eb-8b3e-be2a4a1c987d.mp4

Originally created by @yakobyd on GitHub (Jan 4, 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 ``` Microsoft Windows [Version 10.0.19041.685] Windows Terminal Version: 1.4.3243.0 ``` ## Steps to reproduce <!-- A description of how to trigger this bug. --> **Issue:** The terminal becomes irresponsive after few days of use. Specifically, switching tabs is very slow. I often leave my terminal app open for a week of continuous use. Usually, after three days, the terminal becomes very slow to interact with. This has been happening consistently for the past month. Namely, I have experienced this issue at least four times by now. To reproduce, open the terminal and use it for three days without closing the app. The terminal should become very slow at this point. If one closes the terminal and reopens it, it becomes responsive again. Additional functionalities that become slower: - Typing. - Opening new tabs and closing existing tabs. I have not included these functionalities in the videos below as they are slightly harder to notice. ## Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Below is the behavior of a freshly opened terminal. Note that tab switching is immediate after each click. https://user-images.githubusercontent.com/39068219/103559013-26677800-4ebe-11eb-89fd-c4545bd07f5e.mp4 ## Actual behavior <!-- What's actually happening? --> Below is the behavior of a terminal that was used for three days (I have cleared all output). Note that after clicking, tab switching is very slow. Clicks are not apparent in this video, but I tried to click as soon as the mouse hovers over the tab. Hopefully, the difference is clear when comparing with the expected behavior above. https://user-images.githubusercontent.com/39068219/103559035-2cf5ef80-4ebe-11eb-8b3e-be2a4a1c987d.mp4
claunia added the Resolution-Duplicate label 2026-01-31 03:02:28 +00:00
claunia commented 2026-01-31 03:02:30 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 4, 2021):

@yakobyd - this seems very similar to https://github.com/microsoft/terminal/issues/7710. Please check if they can be "merged".

@Don-Vito commented on GitHub (Jan 4, 2021): @yakobyd - this seems very similar to https://github.com/microsoft/terminal/issues/7710. Please check if they can be "merged".
claunia commented 2026-01-31 03:02:31 +00:00
Author
Owner
Copy Link

@yakobyd commented on GitHub (Jan 4, 2021):

Thanks, indeed, #7710 describes the same problem. I didn't see it was already an open issue, sorry.

@yakobyd commented on GitHub (Jan 4, 2021): Thanks, indeed, #7710 describes the same problem. I didn't see it was already an open issue, sorry.
claunia commented 2026-01-31 03:02:31 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 4, 2021):

Thanks, indeed, #7710 describes the same problem. I didn't see it was already an open issue, sorry.

With more than 1K open issues I also have hard times to find existing ones! 😊
I remembered this one as it is especially popular lately (though I could never repro it).

In any case, I suggest to follow that ticket and resolve this one by now.

@Don-Vito commented on GitHub (Jan 4, 2021): > > > Thanks, indeed, #7710 describes the same problem. I didn't see it was already an open issue, sorry. With more than 1K open issues I also have hard times to find existing ones! :blush: I remembered this one as it is especially popular lately (though I could never repro it). In any case, I suggest to follow that ticket and resolve this one by now.
claunia commented 2026-01-31 03:02:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 5, 2021):

/dup #7710

@DHowett commented on GitHub (Jan 5, 2021): /dup #7710
claunia commented 2026-01-31 03:02:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 5, 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 (Jan 5, 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!
claunia commented 2026-01-31 03:02:32 +00:00
Author
Owner
Copy Link

@yakobyd commented on GitHub (Jan 5, 2021):

Thanks, I will follow the existing ticket.

@Don-Vito - As for reproduction, I use the terminal for ssh + tmux. Similar to https://github.com/microsoft/terminal/issues/7710#issuecomment-719803095, I suspect that excessive command/output history is being saved when using tmux.

Quick check: When printing a large text file during a tmux session, the memory consumption of the terminal process doubles (60MB -> 120MB). After closing the tmux session, and clearing the terminal, there is no way to access the printed text. However, the memory of the terminal process does not clear.

@yakobyd commented on GitHub (Jan 5, 2021): Thanks, I will follow the existing ticket. @Don-Vito - As for reproduction, I use the terminal for ssh + tmux. Similar to https://github.com/microsoft/terminal/issues/7710#issuecomment-719803095, I suspect that excessive command/output history is being saved when using tmux. **Quick check:** When printing a large text file during a tmux session, the memory consumption of the terminal process doubles (60MB -> 120MB). After closing the tmux session, and clearing the terminal, there is no way to access the printed text. However, the memory of the terminal process does not clear.
claunia commented 2026-01-31 03:02:32 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Jan 5, 2021):

g a tmux session, the memory consumption of the terminal process doubles (60MB -> 120MB). After closing the tmux session, and clearing the terminal, there is no way to access

This is extremely interesting - I think this observation needs to be added to the main ticket.
I will also try to do the same to repo locally !
Thanks!

@Don-Vito commented on GitHub (Jan 5, 2021): > g a tmux session, the memory consumption of the terminal process doubles (60MB -> 120MB). After closing the tmux session, and clearing the terminal, there is no way to access This is extremely interesting - I think this observation needs to be added to the main ticket. I will also try to do the same to repo locally ! Thanks!
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 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#11960
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?