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

crash of conhost.exe when removing scrollback buffer #19284

New Issue
Closed
opened 2026-01-31 06:38:58 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:38:58 +00:00
Owner
Copy Link

Originally created by @ssbssa on GitHub (Jan 30, 2023).

Windows Terminal version

No response

Windows build number

10.0.19044.2486

Other Software

No response

Steps to reproduce

Compile and start the following program in a cmd or powershell console:

#include <windows.h>

int main()
{
  HANDLE con = GetStdHandle(STD_OUTPUT_HANDLE);
  CONSOLE_SCREEN_BUFFER_INFO csbi;
  GetConsoleScreenBufferInfo(con, &csbi);

  // start with no scrollback
  COORD con_size = {
    csbi.srWindow.Right - csbi.srWindow.Left + 1,
    csbi.srWindow.Bottom - csbi.srWindow.Top + 1
  };
  SetConsoleScreenBufferSize(con, con_size);

  // add scrollback
  COORD con_scroll_size = {
    con_size.X,
    con_size.Y + 5
  };
  SetConsoleScreenBufferSize(con, con_scroll_size);

  // scroll down 1 line
  SMALL_RECT con_pos = {
    0,
    1,
    csbi.srWindow.Right - csbi.srWindow.Left,
    csbi.srWindow.Bottom - csbi.srWindow.Top + 1
  };
  SetConsoleWindowInfo(con, TRUE, &con_pos);

  // remove scrollback again
  SetConsoleScreenBufferSize(con, con_size); // <- after this conhost.exe crashes

  // small delay so console has time to crash
  Sleep(100);

  // check if console is still here
  if(!GetConsoleScreenBufferInfo(con, &csbi))
    // this returns error code 233 (ERROR_PIPE_NOT_CONNECTED)
    return GetLastError();

  return 0;
}

Expected Behavior

That the console window is still here after the program finished.

Actual Behavior

The console window disappears because conhost.exe crashes.

I see the following in the Event Viewer:

Event 1000, Application Error

Faulting application name: conhost.exe, version: 10.0.19041.1566, time stamp: 0x56b24be3
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x8f8
Faulting application start time: 0x01d9349ec77f207f
Faulting application path: C:\Windows\system32\conhost.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 2debb667-aa6d-443c-a387-96a3ca9b04b4
Faulting package full name: 
Faulting package-relative application ID:

And:

Event 1001, Windows Error Reporting

Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: conhost.exe
P2: 10.0.19041.1566
P3: 56b24be3
P4: ucrtbase.dll
P5: 10.0.19041.789
P6: 2bd748bf
P7: 000000000007286e
P8: c0000409
P9: 0000000000000007
P10:

0xc0000409 is STATUS_STACK_BUFFER_OVERRUN, and 7 is fast failure code FAST_FAIL_FATAL_APP_EXIT.

Originally created by @ssbssa on GitHub (Jan 30, 2023). ### Windows Terminal version _No response_ ### Windows build number 10.0.19044.2486 ### Other Software _No response_ ### Steps to reproduce Compile and start the following program in a cmd or powershell console: ```c #include <windows.h> int main() { HANDLE con = GetStdHandle(STD_OUTPUT_HANDLE); CONSOLE_SCREEN_BUFFER_INFO csbi; GetConsoleScreenBufferInfo(con, &csbi); // start with no scrollback COORD con_size = { csbi.srWindow.Right - csbi.srWindow.Left + 1, csbi.srWindow.Bottom - csbi.srWindow.Top + 1 }; SetConsoleScreenBufferSize(con, con_size); // add scrollback COORD con_scroll_size = { con_size.X, con_size.Y + 5 }; SetConsoleScreenBufferSize(con, con_scroll_size); // scroll down 1 line SMALL_RECT con_pos = { 0, 1, csbi.srWindow.Right - csbi.srWindow.Left, csbi.srWindow.Bottom - csbi.srWindow.Top + 1 }; SetConsoleWindowInfo(con, TRUE, &con_pos); // remove scrollback again SetConsoleScreenBufferSize(con, con_size); // <- after this conhost.exe crashes // small delay so console has time to crash Sleep(100); // check if console is still here if(!GetConsoleScreenBufferInfo(con, &csbi)) // this returns error code 233 (ERROR_PIPE_NOT_CONNECTED) return GetLastError(); return 0; } ``` ### Expected Behavior That the console window is still here after the program finished. ### Actual Behavior The console window disappears because conhost.exe crashes. I see the following in the Event Viewer: ``` Event 1000, Application Error Faulting application name: conhost.exe, version: 10.0.19041.1566, time stamp: 0x56b24be3 Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x8f8 Faulting application start time: 0x01d9349ec77f207f Faulting application path: C:\Windows\system32\conhost.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 2debb667-aa6d-443c-a387-96a3ca9b04b4 Faulting package full name: Faulting package-relative application ID: ``` And: ``` Event 1001, Windows Error Reporting Fault bucket , type 0 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: conhost.exe P2: 10.0.19041.1566 P3: 56b24be3 P4: ucrtbase.dll P5: 10.0.19041.789 P6: 2bd748bf P7: 000000000007286e P8: c0000409 P9: 0000000000000007 P10: ``` 0xc0000409 is STATUS_STACK_BUFFER_OVERRUN, and 7 is fast failure code FAST_FAIL_FATAL_APP_EXIT.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:38:59 +00:00
claunia commented 2026-01-31 06:38:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 30, 2023):

This looks vaguely like #8453 or #9461, which I don't think made its way to 1904x builds. I wonder if there's a simple way for us to have you try out the openconsole.exe (read: conhost) from a newer release and see if that fixes it... You should be able to grab the latest msixbundle and unzip that to grab the OpenConsole.exe out of that, but I don't know if we have a better writeup of how to do that laying around...

@zadjii-msft commented on GitHub (Jan 30, 2023): This looks vaguely like #8453 or #9461, which I don't think made its way to 1904x builds. I wonder if there's a simple way for us to have you try out the `openconsole.exe` (read: conhost) from a newer release and see if that fixes it... You should be able to grab the latest msixbundle and unzip that to grab the OpenConsole.exe out of that, but I don't know if we have a better writeup of how to do that laying around...
claunia commented 2026-01-31 06:39:00 +00:00
Author
Owner
Copy Link

@ssbssa commented on GitHub (Jan 30, 2023):

I've now tried the OpenConsole.exe from Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle.
Yes, with this I can't reproduce the crash any longer, that's great.

But it also has some weird scrolling behavior for some programs now, where whenever I enter some text it scrolls back to some specific location.
Before it only did that if the cursor was below the visible area, but now it also does that when the cursor is already visible.

@ssbssa commented on GitHub (Jan 30, 2023): I've now tried the OpenConsole.exe from Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle. Yes, with this I can't reproduce the crash any longer, that's great. But it also has some weird scrolling behavior for some programs now, where whenever I enter some text it scrolls back to some specific location. Before it only did that if the cursor was below the visible area, but now it also does that when the cursor is already visible.
claunia commented 2026-01-31 06:39:00 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 1, 2023):

Thanks. Glad this helped. I'm gonna close this one out as a /dup of #9461.

Would you mind filing a new issue with repro steps for the other issue you're seeing?

@carlos-zamora commented on GitHub (Feb 1, 2023): Thanks. Glad this helped. I'm gonna close this one out as a /dup of #9461. Would you mind filing a new issue with repro steps for the other issue you're seeing?
claunia commented 2026-01-31 06:39:00 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 1, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 1, 2023): 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#19284
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?