Random blue-ish squares appear on screen #18078

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

Is there any sort of overlay software that's running as a part of your graphics card/? Those boxes don't look like anything the Terminal would ever draw on its own...

This vaguely reminds me of those NVidia ShadowPlay threads - but obviously not the case here.

Maybe something like:

@zadjii-msft commented on GitHub (Aug 1, 2022): Is there any sort of overlay software that's running as a part of your graphics card/? Those boxes don't look like anything the Terminal would ever draw on its own... This vaguely reminds me of those NVidia ShadowPlay threads - but obviously not the case here. Maybe something like: * https://www.amd.com/en/support/kb/faq/dh2-026 * https://appuals.com/remove-grey-box-on-top-right-corner-of-windows-10-desktop/

claunia commented

@237dmitry commented on GitHub (Aug 1, 2022):

Try to play with:

experimental.rendering.forceFullRepaint true or false (default)
experimental.rendering.software true or false (default)

@237dmitry commented on GitHub (Aug 1, 2022): Try to play with: `experimental.rendering.forceFullRepaint` true or false (default) `experimental.rendering.software` true or false (default)

claunia commented

@asineth0 commented on GitHub (Aug 3, 2022):

I've tested with all possible combinations of those two options and the issue still remains. I think it may only happen with more than one tab if that helps.

@asineth0 commented on GitHub (Aug 3, 2022): I've tested with all possible combinations of those two options and the issue still remains. I think it may only happen with more than one tab if that helps.

claunia commented

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

For what it's worth, those experimental rendering settings don't hot-reload (from what I remember). You'd need to open a new tab.

I think it may only happen with more than one tab if that helps.

That's weird for sure. Does that box stay aligned with the top left of the Terminal window, as you move the Terminal window around/?

You might be able to use WinSpy to figure out what that box is, if it's an actual HWND. Use the little finder tool to drag over that box. I'll be stumped if that doesn't find some sort of HWND there (other than the Terminal)

@zadjii-msft commented on GitHub (Aug 3, 2022): For what it's worth, those experimental rendering settings don't hot-reload (from what I remember). You'd need to open a new tab. > I think it may only happen with more than one tab if that helps. That's weird for sure. Does that box stay aligned with the top left of the Terminal window, as you move the Terminal window around/? You might be able to use [WinSpy](http://www.catch22.net/software/winspy) to figure out what that box is, if it's an actual HWND. Use the little finder tool to drag over that box. I'll be stumped if that doesn't find some sort of HWND there (other than the Terminal)

claunia commented

@DHowett commented on GitHub (Aug 4, 2022):

@zadjii-msft those look like pseudowindows...!

In the old days, when you minimized something it actually became Iconic. Like, the window itself changed to rendering just an icon and a name.

After the old days, windows became very tiny. In Windows 95, if you killed Explorer you would see stacks of minimized windows, 60x16 pixels wide, accumulated at the bottom of the screen.

This looks like what might happen if you make a pseudoconsole window visible and minimize it....

@DHowett commented on GitHub (Aug 4, 2022): @zadjii-msft those look like pseudowindows...! In the old days, when you minimized something it _actually became Iconic_. Like, the window itself changed to rendering just an icon and a name. After the old days, windows became very tiny. In Windows 95, if you killed Explorer you would see stacks of minimized windows, 60x16 pixels wide, accumulated at the bottom of the screen. This looks like what might happen if you make a pseudoconsole window visible and minimize it....

claunia commented

@DHowett commented on GitHub (Aug 4, 2022):

@asineth0 are you using any third party window management software?

@DHowett commented on GitHub (Aug 4, 2022): @asineth0 are you using any third party window management software?

claunia commented

@asineth0 commented on GitHub (Aug 4, 2022):

I did a bit of testing and can confirm it goes away with software rendering. Had to completely close out Terminal and reopen it for it to be fixed.

In terms of window management software, the only one I have installed is PowerToys (not sure if that counts).
I tested with it uninstalled and the issue persisted.

@asineth0 commented on GitHub (Aug 4, 2022): I did a bit of testing and can confirm it goes away with software rendering. Had to completely close out Terminal and reopen it for it to be fixed. In terms of window management software, the only one I have installed is PowerToys (not sure if that counts). I tested with it uninstalled and the issue persisted.

claunia commented

@DHowett commented on GitHub (Aug 4, 2022):

Wow, I'm baffled. All of the regions you pointed out are outside the part of Terminal to which software rendering even applies.

Thanks for testing!

@DHowett commented on GitHub (Aug 4, 2022): Wow, I'm baffled. All of the regions you pointed out are _outside_ the part of Terminal to which software rendering even applies. Thanks for testing!

claunia commented

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

confirm it goes away with software rendering

That kinda backs up my theory that this is a graphics card issue. Switching to software rendering got the GPU and any other software out of the way, and the problem went away?

Not sure how we wanna go about this one. We don't' have the hardware to repro and ID the root cause ourselves, and you've got a viable workaround - you okay if we close this out?

@zadjii-msft commented on GitHub (Aug 4, 2022): > confirm it goes away with software rendering That kinda backs up my theory that this is a graphics card issue. Switching to software rendering got the GPU and any other software out of the way, and the problem went away? Not sure how we wanna go about this one. We don't' have the hardware to repro and ID the root cause ourselves, and you've got a viable workaround - you okay if we close this out?

claunia commented

@asineth0 commented on GitHub (Aug 5, 2022):

Yeah, that's fine.

@asineth0 commented on GitHub (Aug 5, 2022): Yeah, that's fine.

claunia commented

@asineth0 commented on GitHub (Aug 9, 2022):

Update: it seems to be happening again even with software rendering. For what it's worth, this is also happening on my laptop which has vastly different specs (Intel i7-5600U & HD 5500).

@asineth0 commented on GitHub (Aug 9, 2022): Update: it seems to be happening again even with software rendering. For what it's worth, this is also happening on my laptop which has vastly different specs (Intel i7-5600U & HD 5500).

claunia commented

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

Huh. Well, then, I would definitely recommend the WinSpy investigation from earlier. That would definitely give us a strong finger to point at whatever is responsible here.

@zadjii-msft commented on GitHub (Aug 11, 2022): Huh. Well, then, I would definitely recommend the WinSpy investigation from earlier. That would definitely give us a strong finger to point at whatever is responsible here.

claunia commented

@ghost commented on GitHub (Aug 15, 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 15, 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**.

claunia commented

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

Holy shit I've got a live repro, at least temporarily. It's on my slaptop, no external displays, rs_wdx_dxp.220811. It's almost definitely a pseudoconsole window, and it's positioned at (0,0)-(18,18), and it's WS_VISIBLE (full styles is 0x94cf0000).

Look real carefully, it's the window frame corners:

Minimizing the terminal makes the box disappear, and restoring brings it back. Only flag it toggles here is WS_MINIMIZE.

I wonder how we got WS_VISIBLE. We shouldn't ever get that, and we should like, always just suppress that.

@zadjii-msft commented on GitHub (Aug 16, 2022): Holy shit I've got a live repro, at least temporarily. It's on my slaptop, no external displays, rs_wdx_dxp.220811. It's almost definitely a pseudoconsole window, and it's positioned at (0,0)-(18,18), and it's WS_VISIBLE (full styles is `0x94cf0000`). Look real carefully, it's the window frame corners: ![image](https://user-images.githubusercontent.com/18356694/184973661-72bdf150-d474-4653-beae-2134e2b4f30b.png) ![image](https://user-images.githubusercontent.com/18356694/184973735-4854fbd5-19d4-4b1c-9852-a9781a44ae26.png) Minimizing the terminal makes the box disappear, and restoring brings it back. Only flag it toggles here is `WS_MINIMIZE`. I wonder how we got `WS_VISIBLE`. We shouldn't ever get that, and we should like, always just suppress that.

claunia commented

@asineth0 commented on GitHub (Aug 16, 2022):

Great! Was starting to think I was crazy since I couldn't pick it up with WinSpy (I probably just don't know what I'm doing lol).

It stopped happening for a few days, but came back. Now I can actually see a window close button.

When not minimized:

When minimized:

@asineth0 commented on GitHub (Aug 16, 2022): Great! Was starting to think I was crazy since I couldn't pick it up with WinSpy (I probably just don't know what I'm doing lol). It stopped happening for a few days, but came back. Now I can actually see a window close button. When not minimized: ![dWJ1wASJBJ](https://user-images.githubusercontent.com/72173894/184974772-38231e93-96c1-49a9-a4b9-315b67f1d7cc.png) When minimized: ![explorer_k803gjmQ5Q](https://user-images.githubusercontent.com/72173894/184974819-bb7d2da0-0079-4abb-a671-f19b99dbd30d.png)

claunia commented

@zadjii-msft commented on GitHub (Sep 1, 2022):

You know what, we've gotten enough feedback at this point that I'm pretty confident that this and #13388 are actually the same thing, just different symptoms. I'll use that thread for tracking. Thanks!

/dup #13388

@zadjii-msft commented on GitHub (Sep 1, 2022): You know what, we've gotten enough feedback at this point that I'm pretty confident that this and #13388 are actually the same thing, just different symptoms. I'll use that thread for tracking. Thanks! /dup #13388

claunia commented

@ghost commented on GitHub (Sep 1, 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 (Sep 1, 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!

claunia commented