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

Bug Report - Crash due to unhandled exception in Microsoft::Console::Render::Renderer::_PaintBufferOutputHelper #3904

New Issue
Closed
opened 2026-01-30 23:32:58 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:32:58 +00:00
Owner
Copy Link

Originally created by @Treit on GitHub (Sep 16, 2019).

Here is the feedback link I filed:
Feedback

Environment

Windows version 10.0.18970.0.
Latest Windows Terminal build (either the available bits or locally built.)

Steps to reproduce

This is the same repro as issue 1360, which I was trying to reproduce and hit this render-related crash instead:

Install ripgrep
Open wt (Windows Terminal), running PowerShell.
Run the following from the root of a large drive
while ($true) { rg -i "foo" }

Expected behavior

The terminal continually runs ripgrep against all files on the drive. It does not crash.

Actual behavior

Eventually the process will crash. If running a debug build, you will get an Assert dialog (Abort, Retry, Ignore) and if you attach a debugger and press Retry you will see the crash is in renderer.cpp at line 642:

STACK_TEXT:
000000058cefd950 00007ffed69d4f99 KERNELBASE!RaiseException+0x69
000000058cefda30 00007ffe9f018337 VCRUNTIME140D!_CxxThrowException+0x137
000000058cefdae0 00007ffe4181ec63 TerminalControl!wil::details::ThrowResultExceptionInternal+0x53
000000058cefdbe0 00007ffe4181ebe9 TerminalControl!wil::ThrowResultException+0x49
000000058cefdc20 00007ffe4181cd85 TerminalControl!wil::details::ReportFailure+0x1e5
000000058ceff1d0 00007ffe4181d131 TerminalControl!wil::details::ReportFailure_Hr+0x91
000000058ceff230 00007ffe41827084 TerminalControl!wil::details::in1diag5::_Throw_Hr+0x74
000000058ceff280 00007ffe418a6e59 TerminalControl!wil::details::in1diag5::Throw_IfFailed+0x69
000000058ceff2c0 00007ffe4193ea77 TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutputHelper+0x3f7
000000058ceff4b0 00007ffe4193e5f4 TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutput+0x394
000000058ceff750 00007ffe4193dd57 TerminalControl!Microsoft::Console::Render::Renderer::_PaintFrameForEngine+0x487
000000058ceff8c0 00007ffe4193bf95 TerminalControl!Microsoft::Console::Render::Renderer::PaintFrame+0xf5
000000058ceff980 00007ffe4193b84a TerminalControl!Microsoft::Console::Render::RenderThread::_ThreadProc+0x8a
000000058ceff9c0 00007ffe4193b7a6 TerminalControl!Microsoft::Console::Render::RenderThread::s_ThreadProc+0x46
000000058ceffa00 00007ffed82c7034 KERNEL32!BaseThreadInitThunk+0x14
000000058ceffa30 00007ffed8ddb1b1 ntdll!RtlUserThreadStart+0x21

FAULTING_SOURCE_FILE: E:\src\git\Terminal\src\renderer\base\renderer.cpp
FAULTING_SOURCE_LINE_NUMBER: 642
SYMBOL_NAME: TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutputHelper+3f7

Originally created by @Treit on GitHub (Sep 16, 2019). Here is the feedback link I filed: [Feedback](https://aka.ms/AA62vzv) # Environment ```none Windows version 10.0.18970.0. Latest Windows Terminal build (either the available bits or locally built.) ``` # Steps to reproduce This is the same repro as issue [1360](https://github.com/microsoft/terminal/issues/1360), which I was trying to reproduce and hit this render-related crash instead: Install [ripgrep](https://github.com/BurntSushi/ripgrep) Open wt (Windows Terminal), running PowerShell. Run the following from the root of a large drive `while ($true) { rg -i "foo" }` # Expected behavior The terminal continually runs ripgrep against all files on the drive. It does not crash. # Actual behavior Eventually the process will crash. If running a debug build, you will get an Assert dialog (Abort, Retry, Ignore) and if you attach a debugger and press Retry you will see the crash is in renderer.cpp at line 642: > STACK_TEXT: 00000005`8cefd950 00007ffe`d69d4f99 KERNELBASE!RaiseException+0x69 00000005`8cefda30 00007ffe`9f018337 VCRUNTIME140D!_CxxThrowException+0x137 00000005`8cefdae0 00007ffe`4181ec63 TerminalControl!wil::details::ThrowResultExceptionInternal+0x53 00000005`8cefdbe0 00007ffe`4181ebe9 TerminalControl!wil::ThrowResultException+0x49 00000005`8cefdc20 00007ffe`4181cd85 TerminalControl!wil::details::ReportFailure+0x1e5 00000005`8ceff1d0 00007ffe`4181d131 TerminalControl!wil::details::ReportFailure_Hr+0x91 00000005`8ceff230 00007ffe`41827084 TerminalControl!wil::details::in1diag5::_Throw_Hr+0x74 00000005`8ceff280 00007ffe`418a6e59 TerminalControl!wil::details::in1diag5::Throw_IfFailed+0x69 00000005`8ceff2c0 00007ffe`4193ea77 TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutputHelper+0x3f7 00000005`8ceff4b0 00007ffe`4193e5f4 TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutput+0x394 00000005`8ceff750 00007ffe`4193dd57 TerminalControl!Microsoft::Console::Render::Renderer::_PaintFrameForEngine+0x487 00000005`8ceff8c0 00007ffe`4193bf95 TerminalControl!Microsoft::Console::Render::Renderer::PaintFrame+0xf5 00000005`8ceff980 00007ffe`4193b84a TerminalControl!Microsoft::Console::Render::RenderThread::_ThreadProc+0x8a 00000005`8ceff9c0 00007ffe`4193b7a6 TerminalControl!Microsoft::Console::Render::RenderThread::s_ThreadProc+0x46 00000005`8ceffa00 00007ffe`d82c7034 KERNEL32!BaseThreadInitThunk+0x14 00000005`8ceffa30 00007ffe`d8ddb1b1 ntdll!RtlUserThreadStart+0x21 > FAULTING_SOURCE_FILE: E:\src\git\Terminal\src\renderer\base\renderer.cpp > FAULTING_SOURCE_LINE_NUMBER: 642 > SYMBOL_NAME: TerminalControl!Microsoft::Console::Render::Renderer::_PaintBufferOutputHelper+3f7
claunia added the Resolution-Duplicate label 2026-01-30 23:32:58 +00:00
claunia commented 2026-01-30 23:32:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 16, 2019):

/dup #2724

@DHowett-MSFT commented on GitHub (Sep 16, 2019): /dup #2724
claunia commented 2026-01-30 23:33:00 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 16, 2019):

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 16, 2019): 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 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#3904
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?