-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Crash report #18084
Comments
That looks like a crash when using the "tray icon". Any chance you were using that feature/? Could you try Terminal Preview 1.22, and see if that fixes this? IIRC there were some stability improvements to the way multiple windows are handled since 1.20. I suspect that might help mitigate this issue. note to self: You're not on Windows 10, so it's not refrigeration related. |
I don't think I touched the tray icon on the first crash. Now I checked the crashes again and I see that the first crash was indeed different. First crash is here: Null deref: Maybe
Call stack:
|
Windows Terminal version
1.20.11781.0
Windows build number
10.0.22631.4317
Other Software
No response
Steps to reproduce
Not sure how to repro, I had this crash multiple times, got me by surprise because I had some batch working and I didn't understand where it went.
I suspect it's related to quake mode (Win+`) which was also difficult to disable, no option in the gui, had to edit json.
The terminal sometimes can run important jobs, if it's killed, it'd be better to have it relaunch or at least reopen in the old cmd, but not kill the underlying job only because some gui failed.
Expected Behavior
No response
Actual Behavior
Crash stack trace, I hope it's enough to understand the problem.
The text was updated successfully, but these errors were encountered: