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

v2 conhost crash with SetConsoleScreenBufferInfoEx calls #377

New Issue
Closed
opened 2026-01-30 21:50:18 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:50:18 +00:00
Owner
Copy Link

Originally created by @rprichard on GitHub (Sep 17, 2018).

Originally assigned to: @miniksa on GitHub.

  • Your Windows build number: [Version 10.0.17760.1]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

Using SetConsoleScreenBufferInfoEx to make the console buffer and window smaller, simultaneously, can crash the v2 conhost with a recent Insiders build.

Steps:

  1. Open a cmd/powershell console window.
  2. Open the console properties and uncheck the "Layout > Wrap text output on resize" option.
  3. Run the test program I included.
  4. The console window disappears.

What's wrong / what should be happening instead:

SetConsoleScreenBufferInfoEx shouldn't crash. The text Hello? should appear, and the console should return control to cmd/powershell.

Aside 1: I don't think this affects winpty at all.
Aside 2: SetConsoleScreenBufferInfoEx seems to handle srWindow differently than both SetConsoleWindowInfo and GetConsoleScreenBufferInfoEx. It tends to set the window size to 1 less width/height than the requested size, so a pair of calls to GetConsoleScreenBufferInfoEx and SetConsoleScreenBufferInfoEx shrinks the console window.

Test program

#include <windows.h>
#include <stdio.h>

int main(int argc, char *argv[]) {

    HANDLE conout = GetStdHandle(STD_OUTPUT_HANDLE);
    CONSOLE_SCREEN_BUFFER_INFOEX info = { sizeof(info) };
    GetConsoleScreenBufferInfoEx(conout, &info);

    info.dwSize.X = 120;
    info.dwSize.Y = 5000;
    info.srWindow.Left = info.srWindow.Top = 0;
    info.srWindow.Right = 121;
    info.srWindow.Bottom = 26;
    SetConsoleScreenBufferInfoEx(conout, &info);

    SetConsoleCursorPosition(conout, COORD { 0, 4000 });

    info.dwSize.X = 80;
    info.dwSize.Y = 20;
    info.srWindow.Right = 41;
    info.srWindow.Bottom = 11;
    SetConsoleScreenBufferInfoEx(conout, &info);

    printf("Hello?\n");

    return 0;
}
Originally created by @rprichard on GitHub (Sep 17, 2018). Originally assigned to: @miniksa on GitHub. * Your Windows build number: [Version 10.0.17760.1] ## What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Using `SetConsoleScreenBufferInfoEx` to make the console buffer and window smaller, simultaneously, can crash the v2 conhost with a recent Insiders build. Steps: 1. Open a cmd/powershell console window. 2. Open the console properties and uncheck the "Layout > Wrap text output on resize" option. 3. Run the test program I included. 4. The console window disappears. ## What's wrong / what should be happening instead: `SetConsoleScreenBufferInfoEx` shouldn't crash. The text `Hello?` should appear, and the console should return control to cmd/powershell. Aside 1: I don't think this affects winpty at all. Aside 2: `SetConsoleScreenBufferInfoEx` seems to handle `srWindow` differently than both `SetConsoleWindowInfo` and `GetConsoleScreenBufferInfoEx`. It tends to set the window size to 1 less width/height than the requested size, so a pair of calls to `GetConsoleScreenBufferInfoEx` and `SetConsoleScreenBufferInfoEx` shrinks the console window. ## Test program ```c++ #include <windows.h> #include <stdio.h> int main(int argc, char *argv[]) { HANDLE conout = GetStdHandle(STD_OUTPUT_HANDLE); CONSOLE_SCREEN_BUFFER_INFOEX info = { sizeof(info) }; GetConsoleScreenBufferInfoEx(conout, &info); info.dwSize.X = 120; info.dwSize.Y = 5000; info.srWindow.Left = info.srWindow.Top = 0; info.srWindow.Right = 121; info.srWindow.Bottom = 26; SetConsoleScreenBufferInfoEx(conout, &info); SetConsoleCursorPosition(conout, COORD { 0, 4000 }); info.dwSize.X = 80; info.dwSize.Y = 20; info.srWindow.Right = 41; info.srWindow.Bottom = 11; SetConsoleScreenBufferInfoEx(conout, &info); printf("Hello?\n"); return 0; } ```
claunia added the Product-ConhostWork-ItemNeeds-Repro labels 2026-01-30 21:50:18 +00:00
claunia commented 2026-01-30 21:50:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 17, 2018):

Thanks for the bug report, I've filed msft:19013486 to make sure this gets fixed ASAP :)

@zadjii-msft commented on GitHub (Sep 17, 2018): Thanks for the bug report, I've filed msft:19013486 to make sure this gets fixed ASAP :)
claunia commented 2026-01-30 21:50:19 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jan 4, 2019):

I'm not able to reproduce this issue anymore. Perhaps we fixed it?

If it's still crashing for you, can you try to find the report ID so I can maybe correlate it?
It should be in the Event Viewer under Windows Logs > Application.

I believe it's Event ID 1000 for Application Error (and should contain conhost.exe as the faulting application path with a report ID GUID that you can give to me).

@miniksa commented on GitHub (Jan 4, 2019): I'm not able to reproduce this issue anymore. Perhaps we fixed it? If it's still crashing for you, can you try to find the report ID so I can maybe correlate it? It should be in the Event Viewer under Windows Logs > Application. I believe it's Event ID 1000 for Application Error (and should contain conhost.exe as the faulting application path with a report ID GUID that you can give to me).
claunia commented 2026-01-30 21:50:19 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 6, 2019):

Closing this for now. If you can get the report ID from a recent repro of this crash, we'd love to take a look. Thanks!

@DHowett-MSFT commented on GitHub (Feb 6, 2019): Closing this for now. If you can get the report ID from a recent repro of this crash, we'd love to take a look. Thanks!
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 Needs-Repro Product-Conhost Work-Item
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#377
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?