-
Notifications
You must be signed in to change notification settings - Fork 675
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
CommandBarFlyout crash fix #5937
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume we can't realistically add a test for this can we? Changes look good to me 🙂
@chingucoding, no repro no test :-( |
Fair enough. |
This reverts commit 03a091b. Undoing CommandBarFlyout changes because of crash regressions.
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
CommandBarFlyout fix for internal bug 35782367.
Crash dumps indicated that the Hide() call was causing a null ref exception. The call occurs when the closing animation completes.
My assumption is that in rare cases the 'this' pointer is no longer valid by the time the closing animation completed and using a weak reference to the CommandBarFlyout instead solves the issue. I have not been able to repro the crash though after trying to get the CommandBarFlyout to be garbage-collected before the Hide call. So I was not able to confirm my assumption.