starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Renderer encountered an unexpected error: -2005270527 #18637

New Issue
Closed
opened 2026-01-31 06:19:54 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:19:54 +00:00
Owner
Copy Link

Originally created by @dovholuknf on GitHub (Oct 10, 2022).

Windows Terminal version

1.15.2713.0

Windows build number

10.0.22621.521

Other Software

ssh'ed to AWS machine, used vim inside there

Steps to reproduce

No idea. I had three terminals in one window arranged in a "pi" pattern:

--------
content
--------
p1 | p2

I had made p1 bigger using ctrl-alt-up/right. I noticed when I hovered over the pane and exited, the bell tripped. everytime i entered the pane, it was fine, but when exiting the pane the bell would trigger

Expected Behavior

No error and no bell firing

Actual Behavior

When I went to vim, the renderer error triggered: Renderer encountered an unexpected error: -2005270527

Strangely when I made the p2 pane bigger again (see above for pane diagram) the error cleared and things worked fine. every key stroke triggered the error and exiting vim was "hard/impossible". Only after making the pane bigger, did the error go away and I could exit vim.

Originally created by @dovholuknf on GitHub (Oct 10, 2022). ### Windows Terminal version 1.15.2713.0 ### Windows build number 10.0.22621.521 ### Other Software ssh'ed to AWS machine, used `vim` inside there ### Steps to reproduce No idea. I had three terminals in one window arranged in a "pi" pattern: ``` -------- content -------- p1 | p2 ``` I had made p1 bigger using ctrl-alt-up/right. I noticed when I hovered over the pane and exited, the bell tripped. everytime i entered the pane, it was fine, but when exiting the pane the bell would trigger ### Expected Behavior No error and no bell firing ### Actual Behavior When I went to vim, the renderer error triggered: Renderer encountered an unexpected error: -2005270527 Strangely when I made the p2 pane bigger again (see above for pane diagram) the error cleared and things worked fine. every key stroke triggered the error and exiting vim was "hard/impossible". Only after making the pane bigger, did the error go away and I could exit vim.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:19:54 +00:00
claunia commented 2026-01-31 06:19:55 +00:00
Author
Owner
Copy Link

@dovholuknf commented on GitHub (Oct 10, 2022):

I think I ran a clear on the left (p1) terminal pane as well as the right (p2) pane. dunno if it's relevant or helpful but maybe

@dovholuknf commented on GitHub (Oct 10, 2022): I think I ran a `clear` on the left (p1) terminal pane as well as the right (p2) pane. dunno if it's relevant or helpful but maybe
claunia commented 2026-01-31 06:19:56 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 10, 2022):

I'll deduplicate this issue with another report that we got a while ago. /dup #14082

@lhecker commented on GitHub (Oct 10, 2022): I'll deduplicate this issue with another report that we got a while ago. /dup #14082
claunia commented 2026-01-31 06:19:56 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 10, 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 10, 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18637
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?