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

Crashes when moved to second screen #3401

Closed
ghost opened this issue Nov 1, 2019 · 2 comments
Closed

Crashes when moved to second screen #3401

ghost opened this issue Nov 1, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ghost
Copy link

ghost commented Nov 1, 2019

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?
Not important

# Steps to reproduce

Laptop DELL XPS 9560 (screen resolution 1920x1080) is connected to an external USB-C LG 4k 27" monitor (LG 27UK650).
Open terminal and move it from the second screen to the laptop's screen and the terminal will close without any error message after 2 seconds.

# Expected behavior

Terminal not to crash when moved to a second display.

# Actual behavior

Terminal closes when moved to a separate display
@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 1, 2019
@zadjii-msft
Copy link
Member

Thanks for the report! This being tracked by a pile of other issues, but the root cause is either #3303 or #2277.

/dup #3303 #2277 #3273 #3355 #3376 #3385

@ghost
Copy link

ghost commented Nov 1, 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 1, 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 Needs-Tag-Fix Doesn't match tag requirements labels Nov 1, 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
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
1 participant
@zadjii-msft