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

Terminal closes itself #2655

Closed
xobs opened this issue Sep 4, 2019 · 20 comments
Closed

Terminal closes itself #2655

xobs opened this issue Sep 4, 2019 · 20 comments
Labels
Area-Quality Stability, Performance, Etc. Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Severity-Crash Crashes are real bad news.

Comments

@xobs
Copy link

xobs commented Sep 4, 2019

Environment

Windows build number: Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.4.2382.0

Any other software? WSL 16.04

Steps to reproduce

Use Terminal

Expected behavior

Terminal shouldn't close unless I tell it to close

Actual behavior

Terminal will occasionally pause for a few seconds, then close, taking with it all of my sessions. I am unsure whether this is a crash or not because it doesn't pop up a crash dialog box. This happens once every day or two.

For example, this just happened while doing a wget

If this is expected behavior, it's not good. If it's a crash, then it should present a dialog box indicating it's a crash, along with something such as a stack trace or crash reason.
@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 Sep 4, 2019
@DHowett-MSFT
Copy link
Contributor

Yeah, that'll be a crash. Unfortunately, when we crash hard, it's somewhat out of our control as to whether we can pop up a dialog.

Would you mind collecting feedback hub info? (Following up with a tag that makes the bot tell you the good word.)

@ghost
Copy link

ghost commented Sep 4, 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-Feedback-Hub labels Sep 4, 2019
@DHowett-MSFT DHowett-MSFT added the Severity-Crash Crashes are real bad news. label Sep 4, 2019
@xobs
Copy link
Author

xobs commented Sep 4, 2019

How do I send feedback? If I click the down-arrow and go to Feedback, it opens a browser and takes me to https://github.com/microsoft/Terminal/issues

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Sep 4, 2019
@DHowett-MSFT
Copy link
Contributor

You'll need to use the Feedback Hub application (sorry, it's a separate app!) It'll help capture diagnostic information that Windows Terminal can't.

@DHowett-MSFT DHowett-MSFT added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Sep 4, 2019
@xobs
Copy link
Author

xobs commented Sep 4, 2019

https://aka.ms/AA5zukj

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Sep 4, 2019
@emc2314
Copy link

emc2314 commented Sep 8, 2019

Same here. Suddenly exit about once a day. Sometimes using vim, sometimes running python. Don't know what's happening. For WSL, terminal crash means power off. Hope it will be fixed soon.

@bitcrazed bitcrazed added Product-Terminal The new Windows Terminal. and removed Severity-Crash Crashes are real bad news. labels Sep 10, 2019
@bitcrazed bitcrazed added this to the Terminal-1909 milestone Sep 10, 2019
@bitcrazed bitcrazed added Severity-Crash Crashes are real bad news. Area-Quality Stability, Performance, Etc. Needs-Attention The core contributors need to come back around and look at this ASAP. Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Attention The core contributors need to come back around and look at this ASAP. 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 Sep 12, 2019
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Sep 12, 2019
@pcolmer
Copy link

pcolmer commented Sep 13, 2019

I'm experiencing Terminal just quitting on me at least once a day but, unfortunately, no particular pattern to it. My usage pattern is the default PowerShell terminal, a WSL terminal and then one or more SSH terminals.

More often than not, I think I have observed that quitting the SSH terminal with CTRL+D can trigger Terminal into dying.

@zadjii-msft
Copy link
Member

This is the same bucket as /dupe #2248

@ghost
Copy link

ghost commented Sep 13, 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 Sep 13, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Tag-Fix Doesn't match tag requirements Needs-Attention The core contributors need to come back around and look at this ASAP. labels Sep 13, 2019
@xobs
Copy link
Author

xobs commented Sep 14, 2019

This seems different from #2248 -- that only happens when opening/closing tabs, whereas I'm experiencing this issue randomly. For example, in the initial bug report I mentioned that it happened while wget was in the middle of transferring files.

@zadjii-msft
Copy link
Member

Well, that's certainly curious. If it crashes during a wget I'd assume that it's actually #2375, though when examining the feedback you sent, the stack was shockingly crashing in the same place as #2248. Maybe they're actually correlated with one another? Impossible to say for sure.

@xobs
Copy link
Author

xobs commented Oct 5, 2019

@zadjii-msft I just had this happen again. I was using riscv64-unknown-elf-gdb and I ran bt to get a backtrace.

@xobs
Copy link
Author

xobs commented Oct 7, 2019

@zadjii-msft is there anything more I should do on this? If not, I'm going to stop using Terminal because having it close randomly when I'm typing characters is severely disruptive to working on terminal programs.

@mcpiroman mcpiroman mentioned this issue Oct 19, 2019
Merged
5 tasks
@zadjii-msft zadjii-msft removed this from the Terminal-1909 milestone Nov 18, 2019
@jiaulislam
Copy link

any solution for this issue yet... now a days I'm facing same issue more frequently.

@zadjii-msft
Copy link
Member

@jiaulislam The original bug that this issue was tracking was resolved more than a year ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).

@joeyjiaojg
Copy link

I opened two windows terminals, and each opened several tabs.

When I'm using remote desktop of another windows machine connect the that host, the terminal window got disappeared.

Edition	Windows 10 Enterprise
Version	20H2
Installed on	‎6/‎3/‎2021
OS build	19042.1288
Experience	Windows Feature Experience Pack 120.2212.3920.0

Windows Terminal
Version: 1.10.2714.0

@victoryhb
Copy link

I can confirm that the same problem still persists in the the latest version of Windows Terminal (Version: 1.15.2875.0). The whole app just randomly disappears into nowhere after several hours in use.

@techierishi
Copy link

Its still there in version 1.16.10262.0. Even on just using powershell, it closes automatically.

@RodrigoSaezCea
Copy link

Its still there in version 1.18.2822.0

@zadjii-msft
Copy link
Member

Please read the thread. The original bug that this issue was tracking was resolved more than 3 years ago. If you're still seeing the Terminal crash randomly on you, then there's probably something new that's the root cause of your issue. I'd recommend filing a new issue, and attaching a feedback hub link (like mentioned earlier in this thread).

@microsoft microsoft locked as resolved and limited conversation to collaborators Nov 17, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Area-Quality Stability, Performance, Etc. Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Severity-Crash Crashes are real bad news.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests