Terminal shows corrupt texture sometimes when resuming the OS from a sleep state

[Tyriar]

Workaround: Press ctrl++ and ctrl+- (mac: cmd++, cmd+-) to zoom VS Code in and out which will do a complete redraw of the terminal.

---

Repro:

1. Open a terminal, run some commands
2. Sleep system
3. Resume the system (I think the delay between 2 and 3 has to be a while)

What happens exactly differs across machines, I've seen full black, full transparent and things like this:

It seems like both the main terminal canvas texture as well as the texture atlas textures can become corrupted.

[jchv]

Does this particular flavor of issue happen outside of Linux with NVIDIA Proprietary drivers? It does seem some people report issues with terminal resume on macOS, but NVIDIA's proprietary drivers on Linux seem to have an endemic issue with sleep/resume.

[Tyriar]

I think I've seen it on my Macbook (Intel UHD Graphics 630 1536 MB) and my home PC on Windows (GTX 600 series I think).

[chrsmrtn-]

I have this too and I'm using the on board video card. Intel HD Graphics 630

[chrsmrtn-]

I resumed from a sleep state and I didn't immediately reproduce this issue.

[chrsmrtn-]

@Tyriar you mentioned a "delay between 2 and 3 has to be a while". Is that 2 to 3 hours? My sleep state duration was just under 2 hours

[Tyriar]

@chrsmrtn- yeah it's pretty hard to reproduce intentionally

[chrsmrtn-]

I've also noted deuteriation of the window. As in initially all is well after my computer wakes back up, but over time artifacts started appearing (using npm packages to host, monitor changes, and auto compile on change). After a while the window flashes and goes black.

[chrsmrtn-]

updated to 1809 and again ran into the issue where the terminal text was no longer visible. I could see a cursor, but interacting (even hitting enter to get the command prompt to print out) didn't work.

I closed and re-opened the terminal, but no text was displayed. I could get the command prompt to display if I hit enter

[chrsmrtn-]

note the above occurred with a working terminal and sleep was not involved. Just like my original ticket that was logged.

[achary]

Same weird artefacts after wake-up from sleep on laptop with NVidia graphics card, Ubuntu 16.04 LTS. Reloading window action is required.

[dan-dr]

@Tyriar Do you have an idea how to fix it? I could PR..

[Tyriar]

I've pushed e531682 which might be a fix for this problem. For those seeing this a lot could you add this to your settings file and let me know if you still observe the problem:

"terminal.integrated.experimentalRefreshOnResume": true

I can make this the default behavior if it works and doesn't cause any other issues.

[connor4312]

I've never seen this so not sure how to repro, any steps?

[meganrogge]

I think it's fine to say this is verified because we now detect if the OS is resuming from sleep and clear the texture to prevent this from happening

[MartinWallgren]

I can verify that this is solved. I used to see this everytime i locked/unlocked my computer. It's not happening anymore.

[dinosaurchi]

I'm still getting this problem with VSCode 1.61.2 on Ubuntu 18.04.5 LTS, where can I get the patch @MartinWallgren ?

[Tyriar]

@dinosaurchi was your problem specifically after OS sleep/resume?

[sguillia]

@Tyriar Still reproduces specifically after OS sleep/resume on 1.62.0-insider

[Tyriar]

@sguillia @dinosaurchi does it fix itself after resizing the terminal, or only when changing zoom level (ctrl++/ctrl+-)?

[dinosaurchi]

@dinosaurchi was your problem specifically after OS sleep/resume?

Yes, when I resumed from sleep or simply login back (not sleep), it happened

@sguillia @dinosaurchi does it fix itself after resizing the terminal, or only when changing zoom level (ctrl++/ctrl+-)?

So far, I fix it by closing the terminal and reopen a new one

• It is inconvenient as all of my bash history will be wiped out

Resizing the terminal does not solve the problem in my case

[sguillia]

does it fix itself after resizing the terminal, or only when changing zoom level (ctrl++/ctrl+-)?

After resizing the terminal, the black squares are gone but some characters are not displayed

Example with ls (notice missing chars on third line)

When changing zoom level (ctrl++/ctrl+-) it works perfectly again

Corrupt texture seems to never happen when terminal was restored (when Session contents restored is in the terminal, I can't reproduce)

[Tyriar]

I guess this is not fixed for some cases then, can you open devtools (Help > Toggle Developer Tools), inspect the terminal and put a screenshot there so we can tell which renderer this is happening on?

[sguillia]

@Tyriar

[Tyriar]

@sguillia oh that's even more interesting, so the webgl renderer fails which I believe just reverts to the DOM renderer for the remainder of the session and that fails for some reason (or it retries?).

[egaznep]

The terminal I left open before suspended my PC

Things are good if I start a new terminal using (+)

Console log upon inspection

I also have the same issue on my PC with Ubuntu 20.04.2, NVIDIA proprietary drivers but I see a different console log upon inspection of the terminal. Similar to what @sguillia experienced I can zoom in to get the contents back.

[simontims]

I see this in 1.64.2 via Remote Desktop with the PowerShell Integrated Console.

1. RDP to a Windows 10 Pro machine running VSCode
2. Have a ps1 file open
3. Have some content in the terminal window
4. Close RDP (don't log out, just close it)
5. Reconnect to the same session. Terminal window is blank with only the cursor present. Cursor responds to carriage returns, clear [return] places the cursor back to the top etc, but no text is visible
6. Ctrl +- Ctrl ++ fixes the issue and reveals text
7. Close the Integrated Console and click Yes when asked if you want to relaunch also fixes this

[lmaxeniro]

I have had such an issue on Ubuntu18.04 for a long time (maybe two years), the simple solution is just to zoom in/out a bit-- it is not much harmful but rather annoying.. would be good to have some solution