Found an access violation crash which always happen.

An item inside list box has a style that:

• sets a binding referencing ListBox ancestor to a property;
• has a trigger with a setter to the same property;
• trigger condition also references ListBox ancestor;
• trigger condition is true just before destroying the view.

My guess is that during IView destruction the condition gets re-evaluated and becomes false.
This causes the original property setter to become active, but its binding seems to reference the already dead listbox.

While this example reproduces the crash during IView destruction, I may have stumbled upon it in other scenarios as well - when only a part of the element tree was being removed, but I'm not 100% sure.