Command Prompt goes black when scrolling up #18296

Closed
opened 2026-01-31 06:09:38 +00:00 by claunia · 12 comments
Owner

Originally created by @nbstrong on GitHub (Aug 24, 2022).

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.

Originally created by @nbstrong on GitHub (Aug 24, 2022). ### 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.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:09:38 +00:00
Author
Owner

@nbstrong commented on GitHub (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 commented on GitHub (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.
Author
Owner

@nbstrong commented on GitHub (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.

@nbstrong commented on GitHub (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.
Author
Owner

@zadjii-msft commented on GitHub (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. /?

@zadjii-msft commented on GitHub (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. /?
Author
Owner

@ghost commented on GitHub (Aug 29, 2022):

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.

@ghost commented on GitHub (Aug 29, 2022): 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**.
Author
Owner

@nbstrong commented on GitHub (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:
image

This is me scrolling up once (one mousewheel click) with the mouse:
image

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

@nbstrong commented on GitHub (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: ![image](https://user-images.githubusercontent.com/13934837/187269328-d2b33af7-b14c-49a8-ab6c-46e354022a43.png) This is me scrolling up once (one mousewheel click) with the mouse: ![image](https://user-images.githubusercontent.com/13934837/187269537-8b54008a-d039-47c0-b375-e836f0f313ca.png) 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](https://github.com/microsoft/terminal/files/9446994/settings.json.txt)
Author
Owner

@zadjii-msft commented on GitHub (Aug 29, 2022):

Wow that's all sorts of messed up.

  • There's no scrollbar?! Why is there no scrollbar?
  • What the heck happened to the invalidation here? image That just looks wrong
  • Why the heck would a single mouse tick scrollToTop? that's not right, unless the system scroll lines parameter was crazy high
  • Is the crash pretty consistent? If so, can you try following the steps in this post to set up automatic crash dumps/? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
@zadjii-msft commented on GitHub (Aug 29, 2022): Wow that's all sorts of messed up. * There's no scrollbar?! Why is there no scrollbar? * What the heck happened to the invalidation here? ![image](https://user-images.githubusercontent.com/18356694/187280169-6ab0f1e1-5a39-49f2-af40-8438fe5d1613.png) That just looks wrong * Why the heck would a single mouse tick scrollToTop? that's not right, unless the system scroll lines parameter was crazy high * Is the crash pretty consistent? If so, can you try following the steps in [this post](https://www.meziantou.net/tip-automatically-create-a-crash-dump-file-on-error.htm) to set up automatic crash dumps/? (For more info, see [this link](https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)) If that works, then you should be able to automatically get a `.dmp` of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
Author
Owner

@nbstrong commented on GitHub (Aug 29, 2022):

My scroll settings are not very high, 3 lines in Windows settings.

Ill get a crash dump as soon as I can.

Edit: The crash is consistent after it messes up but the case of it messing up like this is not completely. But it will happen again I am sure.

@nbstrong commented on GitHub (Aug 29, 2022): My scroll settings are not very high, 3 lines in Windows settings. Ill get a crash dump as soon as I can. Edit: The crash is consistent after it messes up but the case of it messing up like this is not completely. But it will happen again I am sure.
Author
Owner

@ghost commented on GitHub (Sep 2, 2022):

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.

@ghost commented on GitHub (Sep 2, 2022): 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**.
Author
Owner

@j4james commented on GitHub (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.

@j4james commented on GitHub (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`.
Author
Owner

@nbstrong commented on GitHub (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.

@nbstrong commented on GitHub (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.
Author
Owner

@zadjii-msft commented on GitHub (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

@zadjii-msft commented on GitHub (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
Author
Owner

@ghost commented on GitHub (Oct 26, 2022):

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 (Oct 26, 2022): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18296