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

App terminates unexpectedly when moved from high-DPI-Screen to Lower-DPI-Screen #5129

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

Originally created by @MartinStettner on GitHub (Nov 22, 2019).

Environment

Windows Build Number: 10.0.18362.0
WIndows Terminal version: 0.6.2951.0

3 Monitor Setup
- Main Screen High-DPI (Scaling 150%, 3840x2160)
- Left and right: Scaling 100%, 1920x1200

Steps to reproduce

  • Start Terminal
  • Terminal window opens on Main Screen (High DPI, Scaling 150%)
  • Move Window on secondary screen (Scaling 100%)

Expected behavior

  • (Window scales down correctly)
  • Window should stay on second monitor

Actual behavior

  • (Window scales down correctly)
  • Terminal window disappears after around 1 second without message
  • (Process is terminated according to Task Manager/Process Explorer)

Additional information

If I set both screens to the same scaling (either 100% or 150%) the error does not occur.

If I set the secondary screen to 150% and the main screen to 100%, I can move the Window from the (low-scale) main screen to the (150% scaled) secondary screen without problem. When I move the window back to the 100%-Screen, it disappears again.

Originally created by @MartinStettner on GitHub (Nov 22, 2019). # Environment ```none Windows Build Number: 10.0.18362.0 WIndows Terminal version: 0.6.2951.0 3 Monitor Setup - Main Screen High-DPI (Scaling 150%, 3840x2160) - Left and right: Scaling 100%, 1920x1200 ``` # Steps to reproduce - Start Terminal - Terminal window opens on Main Screen (High DPI, Scaling 150%) - Move Window on secondary screen (Scaling 100%) # Expected behavior - (Window scales down correctly) - Window should stay on second monitor # Actual behavior - (Window scales down correctly) - Terminal window disappears after around 1 second without message - (Process is terminated according to Task Manager/Process Explorer) # Additional information If I set both screens to the same scaling (either 100% or 150%) the error does not occur. If I set the _secondary_ screen to 150% and the main screen to 100%, I can move the Window from the (low-scale) main screen to the (150% scaled) secondary screen without problem. When I move the window back to the 100%-Screen, it disappears again.
claunia added the Needs-Author-FeedbackResolution-Duplicate labels 2026-01-31 00:05:47 +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 Needs-Author-Feedback 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#5129
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?