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

[ConPTY] Resizing ConPTY is sometimes ignored if executed near (before/after) a call to attach a client #14198

New Issue
Open
opened 2026-01-31 04:03:33 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:03:33 +00:00
Owner
Copy Link

Originally created by @o-sdn-o on GitHub (Jun 10, 2021).

Windows Terminal version (or Windows build number)

build from source (conhost.exe replaced by OpenConsole.exe)

Other Software

Terminal multiplexer: vtm 0.4.0 (https://github.com/netxs-group/VTM)

Steps to reproduce

Resize ConPTY several times immediately after creation.

In vtm, ConPTY is used as an element within a structure of interconnected elements. This is something like WPF.

The resulting size of the control depends on dynamically added sub-elements, so the final size of the ConPTY is not known at the time of its creation. The size is calculated step by step during the construction of the final object. This is usually two or three very quick iterations after the ConPTY is created.

Here is an example:

Creating a window with powershell. The intermediate size of the ConPTY during creation is 104x11 (~half the window), but by the time the object is created, the ConPTY should be 104x21.

https://user-images.githubusercontent.com/11535558/121590076-501a6180-ca51-11eb-9fea-cb541a51a626.mp4

The following sequence is executed

  • CreatePseudoConsole(104x11 ...
  • CreateProcess( ..powershell...
  • ...
  • ResizePseudoConsole(hPC, 104x11);
  • ...
  • ResizePseudoConsole(hPC, 104x21);

Expected Behavior

ConPTY must be the last requested size.

Actual Behavior

ConPTY is not the last requested size.

Originally created by @o-sdn-o on GitHub (Jun 10, 2021). ### Windows Terminal version (or Windows build number) build from source (conhost.exe replaced by OpenConsole.exe) ### Other Software Terminal multiplexer: vtm 0.4.0 (https://github.com/netxs-group/VTM) ### Steps to reproduce Resize ConPTY ~~several times~~ immediately after creation. In vtm, ConPTY is used as an element within a structure of interconnected elements. This is something like WPF. The resulting size of the control depends on dynamically added sub-elements, so the final size of the ConPTY is not known at the time of its creation. The size is calculated step by step during the construction of the final object. This is usually two or three very quick iterations after the ConPTY is created. Here is an example: Creating a window with `powershell`. The intermediate size of the ConPTY during creation is `104x11` (~half the window), but by the time the object is created, the ConPTY should be `104x21`. https://user-images.githubusercontent.com/11535558/121590076-501a6180-ca51-11eb-9fea-cb541a51a626.mp4 The following sequence is executed - `CreatePseudoConsole(104x11 ...` - `CreateProcess( ..powershell...` - ... - `ResizePseudoConsole(hPC, 104x11);` - ... - `ResizePseudoConsole(hPC, 104x21);` ### Expected Behavior ConPTY must be the last requested size. ### Actual Behavior ConPTY is not the last requested size.
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 Priority-2 Product-Conpty Resolution-Fix-Committed
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#14198
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?