Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
MartinStettner opened this issue Nov 22, 2019 · 4 comments
Closed

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

MartinStettner opened this issue Nov 22, 2019 · 4 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@MartinStettner
Copy link

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.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 22, 2019
@j4james
Copy link
Collaborator

j4james commented Nov 22, 2019

Sounds like #3303.

@DHowett-MSFT
Copy link
Contributor

Absolutely is. /dup #3303. Also, /feedback.

@ghost
Copy link

ghost commented Nov 22, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Nov 22, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 22, 2019
@ghost
Copy link

ghost commented Nov 22, 2019

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Tag-Fix Doesn't match tag requirements labels Nov 22, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MartinStettner @j4james @DHowett-MSFT