-
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 on process exit #11724
Comments
Huh, it's literally just a decremented refcount on a threadpool. I honestly have no idea how that would ever hit.
Looks like it's the main thread, but there aren't any other threads. Does this happen every time you close the Terminal? Are you running Narrator, or Magnifier or something? I have literally no idea how I'd go about debugging this next. This doesn't look like any of the other "crash on exit"s we've been seeing, but this doesn't look like anything in our code in the first place |
Tracked this down on the inside - looks like this is being tracked internally by MSFT:27372787. Actually happens to a pretty broad swath of applications. Also, seemingly doesn't seem to occur on anything newer than |
In case this helps, I can reproduce this exception consistently in Windows Terminal Preview 1.12.2931.0. My Windows version is 10.0.19041.1348, though, so it's older than the expected fix version. Steps to reproduce:
If you're running from within the debugger it should break when the exception is thrown. Otherwise you can see the crash in the Application log of the system Even Viewer. |
That is wild that it's a consistent repro, thanks for that 😀 |
Windows Terminal version (or Windows build number)
1.12.2931.0
Other Software
No response
Steps to reproduce
close terminal
Expected Behavior
No response
Actual Behavior
crash
crash dumps
CrashDumps.zip
call stack
The text was updated successfully, but these errors were encountered: