Windows terminal crashes suddenly without any visual output

[ThakurKarthik]

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

[zadjii-msft]

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

[ghost]

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!

[ghost]

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]

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

[zadjii-msft]

Thanks!

[ThakurKarthik]

@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]

@zadjii-msft any progress over here ?

[zadjii-msft]

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]

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]

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]

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

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