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.

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

Windows terminal crashes suddenly without any visual output #13262

Closed
ThakurKarthik opened this issue Jun 10, 2022 · 11 comments
Closed

Windows terminal crashes suddenly without any visual output #13262

ThakurKarthik opened this issue Jun 10, 2022 · 11 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Repro We can't figure out how to make this happen. Please help find a simplified repro. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.

Comments

@ThakurKarthik
Copy link

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

Ok I can help better if you can guide me on how to give you any error logs. But right now the issue is that windows terminal just closes/crashes without any error feedback. My use case is simple I open the terminal and navigate to some path and open vscode and I keep the terminal open to run some npm commands. I am not sure when but the terminal crashes if I have one or two or multiple tabs open at once.

Expected Behavior

Windows terminal should not crash as I change to multiple directories and if it crashes then I have to open the terminal again and navigate to those paths again.

Actual Behavior

As I mentioned the terminal window crashes

@ThakurKarthik ThakurKarthik added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jun 10, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 10, 2022
@zadjii-msft
Copy link
Member

If you've got a consistent repro, then the Feedback Hub should be able to capture the crash dump. /feedback

@ghost
Copy link

ghost commented Jun 10, 2022

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Jun 10, 2022
@ghost
Copy link

ghost commented Jun 14, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ThakurKarthik
Copy link
Author

The issue is intermittent, feel free to close it for now. I will reopen it back when I can reproduce the issue.

@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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Jun 15, 2022
@zadjii-msft
Copy link
Member

Thanks!

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2022
@zadjii-msft zadjii-msft added Needs-Repro We can't figure out how to make this happen. Please help find a simplified repro. Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely. labels Jun 15, 2022
@ThakurKarthik
Copy link
Author

@zadjii-msft I was able to run the feedback hub recording and (un)fortunately the terminal crashed too, here is the link https://aka.ms/AAh9yy4 Let me know if you need any thing

@ThakurKarthik
Copy link
Author

@zadjii-msft any progress over here ?

@zadjii-msft
Copy link
Member

Sorry, was out on vacation. Just catching up now.

The only crash I'm seeing is for something called AW.WinPC.Updater.exe - any chance you've got something called "Air Watch" installed? I honestly have no idea what that is or why that crashing would bring down the Terminal. Unfortunately, there wasn't really anything else that the Feedback Hub captured about the Terminal, so it seems to suggest that the problem lies outside the Terminal itself...

@simeyla
Copy link

simeyla commented Sep 23, 2023

I've given up on using Terminal since it just crashes and disappears leaving processes still running.
I'm sure it's happening when memory is low, but that's no excuse. I just look for it and it's gone.

I never seem to see anything in EventLog but that doesn't necessarily mean anything since I don't immediately always notice or look.

@kentcb
Copy link

kentcb commented Nov 24, 2023

I'm about to give up too, found this issue when searching for answers. It's happened to me twice today: two separate terminal windows open, each with several tabs. They just disappear without any feedback at all (except I notice things in my dev process stop working, since processes in those terminals are critical).

It's kind of silly that one must be recording to capture the problem, since the problem appears completely random in nature. There should be some kind of ability to turn on a log so one can check retrospectively what caused the crash.

@omair2084
Copy link

omair2084 commented Mar 5, 2024

I experienced the same and landed here.
So, for me the issue is actually automatic updates to the Terminal which causes this problem.
image

I don't click on any update button as in #6726 . As seen from the screenshot, this happened around 2am.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Repro We can't figure out how to make this happen. Please help find a simplified repro. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.
Projects
None yet
Development

No branches or pull requests

5 participants