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

Writing into inactive screen buffer is broken #427

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

Originally created by @alabuzhev on GitHub (Oct 16, 2018).

Originally assigned to: @miniksa on GitHub.

Windows Version 10.0.17763.1

CreateConsoleScreenBuffer function:

A console can have multiple screen buffers but only one active screen buffer. Inactive screen buffers can be accessed for reading and writing, but only the active screen buffer is displayed. To make the new screen buffer the active screen buffer, use the SetConsoleActiveScreenBuffer function.

This functionality is broken - text sent to the inactive screen buffer ends up in the active and thus visible on the screen.

It does not happen in Legacy mode.

A minimal project to reproduce the issue attached.

AlternativeScreenBufferBug.zip

Originally created by @alabuzhev on GitHub (Oct 16, 2018). Originally assigned to: @miniksa on GitHub. Windows Version 10.0.17763.1 [CreateConsoleScreenBuffer function](https://docs.microsoft.com/en-us/windows/console/createconsolescreenbuffer): >A console can have multiple screen buffers but only one active screen buffer. Inactive screen buffers can be accessed for reading and writing, **but only the active screen buffer is displayed**. To make the new screen buffer the active screen buffer, use the SetConsoleActiveScreenBuffer function. This functionality is broken - text sent to the inactive screen buffer ends up in the active and thus visible on the screen. It does not happen in Legacy mode. A minimal project to reproduce the issue attached. [AlternativeScreenBufferBug.zip](https://github.com/Microsoft/console/files/2484841/AlternativeScreenBufferBug.zip)
claunia added the Product-ConhostWork-ItemResolution-Fix-Committed labels 2026-01-30 21:52:06 +00:00
claunia commented 2026-01-30 21:52:07 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Oct 16, 2018):

Thanks. Fortunately/unfortunately you're on a roll and filing bugs faster than I can investigate and fix them.

I have filed this internally as MSFT:19317384. I'll get to it when I have time.

@miniksa commented on GitHub (Oct 16, 2018): Thanks. Fortunately/unfortunately you're on a roll and filing bugs faster than I can investigate and fix them. I have filed this internally as MSFT:19317384. I'll get to it when I have time.
claunia commented 2026-01-30 21:52:07 +00:00
Author
Owner
Copy Link

@alabuzhev commented on GitHub (Oct 21, 2018):

It's worth mentioning that this only happens when running from Visual Studio, which does it through its own VsDebugConsole.exe helper by default.

@alabuzhev commented on GitHub (Oct 21, 2018): It's worth mentioning that this only happens when running from Visual Studio, which does it through its own VsDebugConsole.exe helper by default.
claunia commented 2026-01-30 21:52:07 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 15, 2018):

OK. I've investigated this, crafted a fix, had it reviewed, and checked it in as of today.

I've also installed a variation on the sample you provided into our feature test suite to ensure that we don't mess this up again in the future. Or at least that we don't mess it up in this very specific way. :P

Thank you very, very much for providing the minimal repro code. It dramatically accelerated the pace at which I could turn around this bug.

It should reach Insiders builds in about 3 weeks.

@miniksa commented on GitHub (Nov 15, 2018): OK. I've investigated this, crafted a fix, had it reviewed, and checked it in as of today. I've also installed a variation on the sample you provided into our feature test suite to ensure that we don't mess this up again in the future. Or at least that we don't mess it up in this very specific way. :P Thank you very, very much for providing the minimal repro code. It dramatically accelerated the pace at which I could turn around this bug. It should reach Insiders builds in about 3 weeks.
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 Product-Conhost Resolution-Fix-Committed 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#427
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?