-
Notifications
You must be signed in to change notification settings - Fork 671
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
MenuFlyout crashes in Xaml Islands #3953
Comments
Can you please attach a repro app ? |
Sure, here you go: WpfApp2.zip |
After playing a bit with it, it seems this is triggered when a sub-menu is opened while the animation for opening the previous sub-menu hasn't finished playing. I've had a few crashes not triggered like that, but since the crash is the exact same the fix would probably resolve them too. |
FYI this looks related to #3529 and #3530, and is probably the root cause for microsoft/terminal#8238 |
@Austin-Lamb and @JesseCol for the XamlIslands perspective |
I found a workaround: #3529 (comment) |
Seems to be fixed in Windows 11, would appreciate the fix to be backported to Windows 10. |
@Austin-Lamb Any way you could confirm that this is fixed in Win11? the Terminal team would greatly appreciate a backport for that fix to Win10 (if that's even possible). Feel free to ping me on a mail thread if needed. |
At least from my testing, I could reliably get it to crash in 10 and can't no matter how hard it try on 11. I wonder if this fix was prompted by the taskbar dogfooding Xaml islands. |
(fyi Austin is out for the week, maybe @JesseCol can answer in his place) |
Hi -- sorry, this bug doesn't ring a bell to me. If it's related to the animation, @codendone might recognize it. |
I believe @gegao18 was the one who fixed this. |
Duplicate of #3529 |
Describe the bug
When opening submenus in quick succession in MenuFlyout on Xaml Islands, there is a chance it can crash the whole program.
Steps to reproduce the bug
Microsoft.Toolkit.Wpf.UI.XamlHost
NuGet package.<compatibility>
add<maxversiontested Id="10.0.19041.0" />
Expected behavior
The app does not crash
Screenshots
![](https://camo.githubusercontent.com/e54711971a769ea8a53aa6c9bba99f719c205058947b268b0cf4bea5363831ce/68747470733a2f2f796966662e666f7273616c652f4d61726f6f6e476f7267656f757343686572756269)
Version Info
NuGet package version:
[Microsoft.Toolkit.Wpf.UI.XamlHost 6.1.2]
Windows app type:
Additional context
This also happens in my C++-based XAML islands app, so this is not an issue specific to the WCT WPF host, it just makes reproduction easier.
Here's a video recording of the issue: https://imgur.com/pHTPAB2
The text was updated successfully, but these errors were encountered: