Terminal becomes extremely laggy after printing large amount of CJK characters

[fireattack]

Windows Terminal version

1.20.11381.0

Windows build number

10.0.19045.4412

Other Software

No response

Steps to reproduce

s = '打印一个非常长的中文句子，啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊'
for _ in range(100):
    print(s)

var s = '打印一个非常长的中文句子，啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊'
for (var i = 0; i < 100; i++) {    console.log(s)    }

Run any of the above script (python or node) in a WT tab.

Expected Behavior

It prints all the lines very quickly and you can scroll the window with ease.

Actual Behavior

It becomes very laggy (takes seconds to print the whole thing) and after printing, the whole window becomes very laggy, you can barely scroll back and forth.

---

So, this problem is tricky because I can't find a reliable way to reproduce it.
All I can confirm is that:

The issue only started to happen in recent months.

It usually starts to happen after I use my computer for extended time (I leave my computer on 24/7). And once it started to appear, it will affect all the Terminal windows, old or new. And it does not matter which type, can reproduce in CMD, PS, PS7 etc.

Furthermore, once the bug appears, the only way I can fix it is by restarting my computer.

It only happens when printing large amount CJK characters (Chinese, Japanese, etc.). Printing ASCII characters are fine.

[crazyGru]

1. Close all instances of Windows Terminal.
2. Delete the settings file located at %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json.
3. Restart Windows Terminal, which will generate a new settings file with default settings.

[lhecker]

You may be running out of GPU memory. The next time this happens can you check your GPU memory usage in Task Manager?

[DHowett]

Can you confirm whether you are using the "new text rendering engine", or whether you have it disabled? Version 1.20 will be the last version with the old text rendering engine, so it will be important to know if the issue is with the new one.

[fireattack]

Yes, I'm using the new "AtlasEngine":

As for GPU memory, I think it's unlikely since I have a 16GB RTX 4060Ti, but I can check it next time this happened.

The full settings.json is also attached but nothing unusual.