Repository navigation
Command Prompt goes black when scrolling up #13840
Description
Windows Terminal version
1.14.1962.0
Windows build number
10.0.19044.1889
Other Software
No response
Steps to reproduce
Print a large amount of data to the command prompt (history may need to be 999999 depth).
Scroll up.
Expected Behavior
Should scroll up to view the data
Actual Behavior
Screen goes black. It returns to normal when hitting enter.
Activity
nbstrong commentedon Aug 24, 2022
Not sure if I should file a separate issue but Windows Terminal also crashes if I try to CLS at this point.
nbstrong commentedon Aug 24, 2022
I feel a bit silly, I went to reproduce it to get screenshots and cannot now. I had been encountering this all day. Will update with screenshots when I see it again.
zadjii-msft commentedon Aug 25, 2022
I'll let the bot give you a week to get a consistent repro☺️ Might be helpful to have you share your settings.json with us too, just in case. /?
nbstrong commentedon Aug 29, 2022
Well this seems to be related though not the exact issue of it going blank.
This is the original screen after printing out 32765 lines of output:
This is me scrolling up once (one mousewheel click) with the mouse:
As you can see it scrolls up 30000 lines and the prompt now appears at the top of the screen.
CLS also crashed Windows Terminal after this.
Here is my settings.json.
settings.json.txt
zadjii-msft commentedon Aug 29, 2022
Wow that's all sorts of messed up.
.dmpof the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!7 remaining items
j4james commentedon Sep 6, 2022
FYI, this might be related to the crash in #13499. At least some of the comments there are from users who say they have a large scrollback history, and that the terminal ends up crashing (or at least freezing) when they use
clear.nbstrong commentedon Sep 6, 2022
Unfortunately what I was doing previously to produce it is no longer possible due to project changes, I was reading a bunch of data from a uart via python to produce it and that uart is now elsewhere.
Tried to do the same by just printing dummy data to the console but no luck.
zadjii-msft commentedon Oct 26, 2022
Hmm. Without a live repro, I'm inclined to just assume that whatever you were seeing here was one of the other crash/hangs we're tracking, and close this thread out. Let's just hope whatever you were seeing gets fixed when we fix the other bugs here.
/dup #13499