.NET 10 Native AOT cause WinUI 3 / UWP App run not responsed

[Gaoyifei1011]

Description

.NET 10 Native AOT cause WinUI 3 / UWP App run not responsed

--------------------

.NET 10 Native AoT 导致 WinUI 3 / UWP 应用运行未响应

---

Steps To Reproduce

App1.zip

I made a simple example to reproduce the bug. This is a simple WinUI 3 desktop application. After running the program, there is a button. The event corresponding to this button is to create a ContentDialog and add it to the Children property of the Grid (to simulate increasing the process's running memory). After clicking three to four times, when the process memory reaches 50-80 MB, the application does not respond. You can try to reproduce this BUG

--------------------------

我制作了一个简单的示例用来复现 bug，这是一个简单的 WinUI 3 桌面应用程序，运行程序后有一个按钮，该按钮对应的事件是创建 ContentDialog 并添加到 Grid 的 Children 属性中（用以模拟增加进程运行内存），点击三到四次后，进程内存到达 50-80 MB 时，应用程序运行未响应，您可以尝试复现一下该 BUG

QQ20251118-078.mp4

---

Expected Behavior

.NET 10 running WinUI 3 / UWP applications will not fail to respond

--------------------------

.NET 10 运行 WinUI 3 / UWP 应用程序不会未响应

---

Version Info

.NET 10.0.0 Stable
CsWinRT 2.2.0
Windows SDK 10.0.26100.6901
Windows 11 26220.7070

Additional Context

Relative issues link（相关问题链接）

dotnet/runtime#121704
dotnet/runtime#121590
dotnet/runtime#121538

[manodasanW]

See update here: dotnet/runtime#121590 (comment). The current assumption is this specific issue occurs when publishing to AOT with debug and is a result of dotnet/runtime#121538. When publishing to AOT with release, this issue is not seen.