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 immediately after launch #10303

Closed
guyrleech opened this issue Jun 1, 2021 · 4 comments
Closed

Crashes immediately after launch #10303

guyrleech opened this issue Jun 1, 2021 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@guyrleech
Copy link

Was running fine before I hibernated my Win10 21H1 laptop but I noticed the existing Windows Terminal window was no longer present after resuming and every time I launch it, it crashes immediately. I have seen this once before but it is usually fine after resume from hibernation. I have full process dumps (95MB zipped). Attached is the windbg !analyze -v output but obviously doesn't tell me much as I don't have symbols for it. I have version 1.8.1444.0 according to the Store app.

windowsterminal crash.TXT
@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 Jun 1, 2021
@microhod
Copy link

microhod commented Jun 1, 2021

I'm seeing the same behaviour on 1.8.1444.0 - I open the app, it waits a couple seconds and crashes.

I'm on Win10 2004 19041.985

@joeykins82
Copy link

Same issue: Terminal 1.8.1444.0 on Win10 2020H2 19042.985

@zadjii-msft
Copy link
Member

Thanks for the !analyze! From the stack, this looks like /dup #10211. A Repair of the app might help you, or setting the default profile's fontFace to something other than the Cascadia family of fonts. Hopefully the hotfix should be shipping today or tomorrow.

@ghost
Copy link

ghost commented Jun 1, 2021

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 Jun 1, 2021
@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 Jun 1, 2021
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
4 participants
@guyrleech @zadjii-msft @joeykins82 @microhod