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

GetConsoleScreenBufferInfoEx + SetConsoleScreenBufferInfoEx screws up the size #18844

New Issue
Open
opened 2026-01-31 06:26:05 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:26:05 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Nov 8, 2022).

Windows Terminal version

1.16.2641.0

Windows build number

10.0.19044.2006

Other Software

No response

Steps to reproduce

  1. Compile the following little program:
#include <cassert>
#include <windows.h>

int main()
{
	for (;;)
	{
		const auto out = GetStdHandle(STD_OUTPUT_HANDLE);
		CONSOLE_SCREEN_BUFFER_INFOEX csbi{ sizeof(csbi) };

		if (!GetConsoleScreenBufferInfoEx(out, &csbi))
			assert(false);

		if (!SetConsoleScreenBufferInfoEx(out, &csbi))
			assert(false);

		system("pause");
	}
}
  1. Run it.
  2. Follow the instructions on the screen.

Expected Behavior

Nothing should happen, because nothing has been changed in the structure.

Actual Behavior

In conhost: the window size decreases on each iteration, eventually the window disappears.
In WT: the buffer size decreases on each iteration, eventually OpenConsole crashes.

More

The issue is not synthetic: CSBI allows to change other information than window/buffer sizes, e.g. the color palette (I know that OSC 4 exists).
If I am only changing the palette, I do not expect changes in the sizes.

Ironically, sequential SetConsoleScreenBufferSize + SetConsoleWindowInfo calls seem to work as expected:

#include <cassert>
#include <windows.h>

int main()
{
	for (;;)
	{
		const auto out = GetStdHandle(STD_OUTPUT_HANDLE);
		CONSOLE_SCREEN_BUFFER_INFOEX csbi{ sizeof(csbi) };

		if (!GetConsoleScreenBufferInfoEx(out, &csbi))
			assert(false);

		// These work fine in any order
		if (!SetConsoleScreenBufferSize(out, csbi.dwSize))
			assert(false);

		if (!SetConsoleWindowInfo(out, true, &csbi.srWindow))
			assert(false);

		system("pause");
	}
}
Originally created by @alabuzhev on GitHub (Nov 8, 2022). ### Windows Terminal version 1.16.2641.0 ### Windows build number 10.0.19044.2006 ### Other Software _No response_ ### Steps to reproduce 1. Compile the following little program: ```C++ #include <cassert> #include <windows.h> int main() { for (;;) { const auto out = GetStdHandle(STD_OUTPUT_HANDLE); CONSOLE_SCREEN_BUFFER_INFOEX csbi{ sizeof(csbi) }; if (!GetConsoleScreenBufferInfoEx(out, &csbi)) assert(false); if (!SetConsoleScreenBufferInfoEx(out, &csbi)) assert(false); system("pause"); } } ``` 2. Run it. 3. Follow the instructions on the screen. ### Expected Behavior Nothing should happen, because nothing has been changed in the structure. ### Actual Behavior In conhost: the window size decreases on each iteration, eventually the window disappears. In WT: the buffer size decreases on each iteration, eventually OpenConsole crashes. ### More The issue is not synthetic: CSBI allows to change other information than window/buffer sizes, e.g. the color palette (I know that `OSC 4` exists). If I am only changing the palette, I do not expect changes in the sizes. Ironically, sequential `SetConsoleScreenBufferSize` + `SetConsoleWindowInfo` calls seem to work as expected: ```C++ #include <cassert> #include <windows.h> int main() { for (;;) { const auto out = GetStdHandle(STD_OUTPUT_HANDLE); CONSOLE_SCREEN_BUFFER_INFOEX csbi{ sizeof(csbi) }; if (!GetConsoleScreenBufferInfoEx(out, &csbi)) assert(false); // These work fine in any order if (!SetConsoleScreenBufferSize(out, csbi.dwSize)) assert(false); if (!SetConsoleWindowInfo(out, true, &csbi.srWindow)) assert(false); system("pause"); } } ```
claunia added the Product-ConhostResolution-By-DesignIssue-BugArea-Server labels 2026-01-31 06:26:06 +00:00
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 Area-Server Issue-Bug Product-Conhost Resolution-By-Design
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#18844
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?