terminal: Renderer encountered an unexpected error: -2005270527
Windows Terminal version
1.16.2642.0
Windows build number
10.0.22000.978
Other Software
No response
Steps to reproduce
- Have a session open (this one is powershell running OpenSSH to a Linux VM)
- Suspend the system
- Wake the system
After resuming, I continuously get the following error: Renderer encountered an unexpected error: -2005270527
. Dismissing it just causes it to come up again. I tried dismissing it about 20 times and it didn’t clear.
Expected Behavior
No errors.
Actual Behavior
Repeated continuous popups of the following error:
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 42 (17 by maintainers)
@lhecker Your posted version Version: 1.18.1443.0 seems to fix everything.
To be clear I was facing at least 3 distinct issues:
I think I was getting confused by 2 and 3 together, because I thought the series of blocks/bars was my cursor, but it was just what the terminal was spitting out instead of the normal prompt of my text.
In PowerShell if I run the given
"$([char]0x1b)]11;rgb:7f/7f/7f$([char]0x1b)\"
command the screen turns grey with light grey text, but the cursor is visibly flashing.Everything seem entirely fixed now with 1.18.1443.0 while using the AtlasEngine.
Yep that’s for sure. The way the old text renderer uses
IDXGISwapChain::Present
is a lot more primitive. But does using “Atlas” with the custom preview build I linked above solve the issue? It’s okay if you don’t want to use such a custom version of course. 🙂 We’ll likely release an update sometime soon. We do intend to make the new text renderer the default with 1.19 and any help we can get to test it would be extremely appreciated!If anyone is still experiencing this issue in the latest Terminal versions, please let me know! I’ll close this issue as resolved in a week otherwise. 🙂
You can also just try:
in the settings. That should switch back to the old renderer
I have this problem intermittently as well and am also running windows terminal preview 1.16.2642.0.
In my case I hibernate, as opposed to sleep, my machine. I tend to find the error occurs when I resume a tmux session, but I just happened to get the problem just now when I went into vim from a local bash shell.
What I find is that if I resize the main window after the error is shown, then it’s not shown again for the rest of the session.
It might be related but I also sometimes find that, after resuming, my tmux session doesn’t seem to know the window size correctly, for example it puts the tmux status bar on the wrong row. Again, resizing the main window fixes that problem.
FYI: If you use “Caskaydia Cove” from the Nerd Fonts website, I found that it had a lot (really, a lot) of subtle issues at least until a few months ago, whereas Delugia is almost flawless and extremely close to the original Cascadia Code. Delugia is sort of what Caskaydia Cove is based on, and I can only recommend trying it out.
@chrisl8 Ah I think I misunderstood you. The way you describe this issue:
made it sound like #15427. But what you wrote afterwards:
makes it instead sound like you’ve been victim of our somewhat confusing “settings layering” where the per-profile settings “override” the settings in the “Defaults” profile and you need to reset the per-profile ones for the “Defaults” to take effect. So I guess it’s not really a rendering issue after all!
Otherwise, you can always confirm if you use the full-featured, performant Direct3D renderer, or the slower Direct2D renderer by running this in a new PowerShell tab:
It doesn’t matter if it’s the old “powershell.exe” or the new “pwsh.exe”. If the cursor is visible afterwards, you’re using Direct3D and if it’s invisible Direct2D. #15427 only affects the Direct2D renderer.
I just tried your “totally not sketchy” build (i verified it was signed by MS 😃 ) and it crashes…
I’ve got this upon error: 00000001 0.00000000 [18696] DXGI ERROR: IDXGISwapChain::Present: Partial Presentation (using scroll or dirty rects) is not valid until first submitting a regular Present without scroll or dirty rects. Otherwise, the preserved back-buffer data would be uninitialized. [ MISCELLANEOUS ERROR #105: ]
Got this issue “Renderer encountered an unexpected error: -2005270527” on the latest Terminal Preview [v1.18.1421.0] Repro: start nvim in WSL ubuntu
I fixed that issue here: #15262 It’s a somewhat annoying bug, so I’ll try to get it merged soon. I‘m super happy to see you try out the main branch btw! I hope there aren’t any serious issues apart from that one. 😊
I get this unexpected error when running
oh-my-posh debug
in maximized window (maximized before running the command) with “AtlasEngine” enabled.DebugView shows the following message when the pop-up shows up:
Terminal version: ae7595b (Release, x64), can’t reproduce in 1.16.10261.0 Windows build number: 19045.2846 oh-my-posh version: 15.4.0
oh-my-posh theme
Theme uses symbols from Nerd Fonts v3 (used font was CaskaydiaCove Nerd Font), but the bug can be reproduced even with the default font.