Taken from a larger example,
[code]
<Menu IsMainMenu="False">
<MenuItem ItemsSource="{Binding Items}">
<MenuItem.ItemContainerStyle>
<Style TargetType="{x:Type MenuItem}" BasedOn="{StaticResource MenuItem}">
<Style.Triggers>
<DataTrigger Binding="{Binding Property}" Value="False">
<Setter Property="Header" Value="{Binding Header}"/>
</DataTrigger>
<DataTrigger Binding="{Binding Property}" Value="True">
<Setter Property="Header">
<Setter.Value>
<TextBlock/>
</Setter.Value>
</Setter>
</DataTrigger>
</Style.Triggers>
</Style>
</MenuItem.ItemContainerStyle>
</MenuItem>
</Menu>
[/code]
crashes Unity to desktop when it is destroyed (such as when the underlying viewmodel is changed). I suspect that the control created by the inactive setter is retained therein even after it is destroyed creating an invalid but retained reference that crashes the system upon its reuse. Refactoring this to use a datatemplate avoids the crash.