Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal tabs can become very sluggish/unresponsive #8640

Closed
NeilMacMullen opened this issue Dec 23, 2020 · 3 comments
Closed

Terminal tabs can become very sluggish/unresponsive #8640

NeilMacMullen opened this issue Dec 23, 2020 · 3 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@NeilMacMullen
Copy link

Environment

Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0
Windows Terminal Preview Version: 1.5.3242.0

Steps to reproduce

Open a windows terminal with multiple tabs (In my case 4 powershell tabs). At least one of the tabs should produce large amounts of output.

Expected behavior

Switching between tabs should be fast and fluid

Actual behavior

Over time (6-24 hours) , the terminal becomes slower and slower to respond to clicks on the tab headers - eventually it can take >10 seconds to switch tabs after a click. The '+' and "open menu" controls in the title bar are similarly unresponsive.

Even if all the tabs are removed and new empty tabs are added, switching remains extremely slow. Note that the problem is limited to the particular terminal instance though - if another instance is opened on the same machine, it is performant and other applications are responsive. Task manager shows no obvious CPU/Memory load.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 23, 2020
@NeilMacMullen
Copy link
Author

The issue also affects keyboard input - when typing into the terminal keystrokes can take a couple of seconds to appears. As described above, other terminal instances and applications are not affected.

@skyline75489
Copy link
Collaborator

We have seen similar reports, noticeably #7710. It's holiday season now, so the response from the team may be delayed.

@NeilMacMullen
Copy link
Author

@skyline75489 Thanks - looking at ##7710 I agree this is almost certainly a duplicate of that. I'll add further findings there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants