Title bar API causes apps to crash on Windows 10 (less often on Windows 11)

[wbokkers]

Describe the bug

On Windows App SDK 1.5.8 (and possibly on 1.6 as well) users experience crashes in (child) windows using title bar customization.

Steps to reproduce the bug

1. I have this code in the constructor of a Window:

     if (AppWindowTitleBar.IsCustomizationSupported())
     {
             _appWindow.TitleBar.ExtendsContentIntoTitleBar = true;
             _appWindow.TitleBar.IconShowOptions = IconShowOptions.HideIconAndSystemMenu;
     }

2. User opens (closes?) this Window
3. The app crashes on Windows 10.0.10945.5131 (But sometimes also on newer Windows 11 versions)

Expected behavior

No crash

NuGet package version

WinUI 3 - Windows App SDK 1.5.8

Windows version

Windows 10.0.19045.5131 (frequent). On Windows 11 less often.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Open similar issues:

• App with custom titlebar crashes after a window is closed. (#10074), similarity score: 0.83
• ExtendsContentIntoTitleBar causes the crash of the app when closing in minimized state (#10103), similarity score: 0.82

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[wbokkers]

I can reproduce one situation on my end:

Enqueue method to show the window with the adapted titlebar
Immediately afterwards enqueue method to close the window (window.Close)
Immediately afterwards enqueue method for showing the window again

This will often result in this crash:

[karkarl]

I have also been reproing this issue, and have started a thread with the AppWindow folks on this.

[wbokkers]

@hiteshkrmsft Are you kidding me? @karkarl Is able to reproduce this issue. And now it is tagged as 'not repro'?

[codendone]

@wbokkers The closing of this issue was done via a script mirroring the state of the internal bug. The person who resolved the issue should have added a comment here. This is what was said in the internal bug:

Does not repro with current 1.7 bits.

I'm not sure if that means 1.7-experimental2 or perhaps more recent builds.

[wbokkers]

@codendone Helpful as always, Thanks! I take it that this has been solved now.