-
Notifications
You must be signed in to change notification settings - Fork 296
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
Background threads are not terminating during _Extension.OnDisconnection #1716
Labels
technical-debt
This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
Comments
Stack trace (mainly so I don't have to catch and dump it again):
|
@comintern was this fixed with #1780? |
This seems to have been fixed in the last couple days. Possibly by #1813? |
Vogel612
added
technical-debt
This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
and removed
technical-debt
This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
quality-control
labels
Nov 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
technical-debt
This makes development harder or is leftover from a PullRequest. Needs to be adressed at some point.
Discovered this when I was doing some testing on how COM objects get released in the GC, and confirmed while testing a putative fix for #1710. This is very likely the cause of some of the weird shutdown errors, i.e. #1710, #1633, #1533, and #1438 (might be more, that's just a quick scan). These appear to be reporting "random" exceptions when closing because the exception that gets thrown would depend on the what the background thread is doing when tries to access something that the main thread has already torn down.
The text was updated successfully, but these errors were encountered: