Preventing deadlock on AppDomain.Unload by removing superfluous finalization logic which uses Dispatcher. #1584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The FlipView and the MetroTabItem contain finalizers which don't clean-up unmanaged resources. All they do is deregister a local handler from a local event, which is quite superfluous. What's more, is that the deregistration was done through the dispatcher. This can lead to a deadlock when unloading an AppDomain (btw., the deadlock is resolved. After a while
AppDomain.Unload(..)
throws an exception stating that it can't unload the domain).The
FlipView
finalizer was originally introduced by commit b5aac16.As far as i can tell the finalizer is not related to the issue which was handled by said commit Fixed a bug where the FlipView was unloaded by the TabControl but it`s inner events weren't reattached when the Tabitem was switched back