Considerable input (typing) lag after lots of output

cklutz commented 7 months ago

Windows Terminal version

1.19.230925002-preview

Windows build number

10.0.19045.0

Other Software

PowerShell Core 7.4.0

Steps to reproduce

In a pane enter some text/commands. Hence, the "typical" input speed. Using movement commands or simply typing random text is OK.
In the same pane, run commands that produce "lots of"(!) output. Like repeatedly run large/long builds (msbuild /v:d). It is hard to quantify, but I would say at least couple of 10.000 lines, over the course of a day maybe.
Again in the same pane, enter text, move cursor, etc. Performance has degraded considerably. Typing is barely possible, time between hitting the key and visual output are at least a couple of seconds.

When you close the pane and open a new one, (or use a another pane or tab in the same Terminal instance), everything is normal. Only the pane with lots of output is affected it seems.

Note: I have seen this behavior with older versions of Terminal (and PowerShell) and Windows, it is only now that I report it. I'm aware that it might be something environmental or not Terminal related, but I haven't found any existing issue in this or other repos.

Expected Behavior

No recognizable input lag.

Actual Behavior

Considerable input lag.

cklutz commented 7 months ago

Update: I will leave this here for now, but it looks as if this is really a PowerShell issue. If in the above set, I launch (from inside the "slow shell") CMD.EXE typing feels normal.

If I find more (concrete) evidence, I'll close this one.

pryorda commented 6 months ago

I have the issue with running wsl and cmd. I dont have the issue in vs-codes terminal

zadjii-msft commented 6 months ago

Hmm, I'm concerned that there's actually a regression here, especially with the recent comments in #11916 too.

Would any of you be able to install a v1.18.10301.0 build, and double check if 1.18 doesn't show this/? (you should be able to just double-click run windowsterminal.exe in the .zip in that release to run 1.18 side-by-side).

cklutz commented 6 months ago

I'd like to that, but I'm no longer at a PC for the next two weeks. I can try it then.

microsoft-github-policy-service[bot] commented 6 months ago

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.

microsoft / terminal