We have an application on Winui3, android and ios. It uses MvvmCross as the platform to manage the viewmodels.

While the applicatin is usually working fine, we have noticed a freeze can happen when running on a remote desktop (RDP). The specific situation is as follows:

1. Open the application
2. Go to a setting screen
3. Change a value and save it
4. Set your focus on a window outside the RDP session (e.g. a browser instance on your computer), but don't minimize the RDP window (so you need 2 screens at least)
5. After approx 5 minutes click on another field in the application
6. The application doesn't response to anything for up to a minute, afterwards it executes all the actions you have clicked on (so if you clicked on a button multiple times it will execute multiple times)

I can reproduce this hang/freeze in debug mode as well as release mode. But when done in debug mode, if I pause the app I get to see the stack trace as seen below. I am a bit stuck on what I can do next to figure out where the issue lies (with us or with winui3). I have tried to replicate the issue with the winui 3 sample app but no luck so far.

Does anyone have an idea where to look next?

We have an application on Winui3, android and ios. It uses MvvmCross as the platform to manage the viewmodels.

While the applicatin is usually working fine, we have noticed a freeze can happen when running on a remote desktop (RDP). The specific situation is as follows:

1. Open the application
2. Go to a setting screen
3. Change a value and save it
4. Set your focus on a window outside the RDP session (e.g. a browser instance on your computer), but don't minimize the RDP window (so you need 2 screens at least)
5. After approx 5 minutes click on another field in the application
6. The application doesn't response to anything for up to a minute, afterwards it executes all the actions you have clicked on (so if you clicked on a button multiple times it will execute multiple times)

I can reproduce this hang/freeze in debug mode as well as release mode. But when done in debug mode, if I pause the app I get to see the stack trace as seen below. I am a bit stuck on what I can do next to figure out where the issue lies (with us or with winui3). I have tried to replicate the issue with the winui 3 sample app but no luck so far.

Does anyone have an idea where to look next?

• c#
• mvvmcross
• freeze
• winui-3

Share Improve this question Follow edited Mar 7 at 10:08 Simon Mourier 140k2222 gold badges263263 silver badges312312 bronze badges asked Mar 7 at 9:37 Joost JensJoost Jens 10477 bronze badges 9

• Difficult to help w/o a reproducing project. I note you seem to have a lot of "external code" threads (with a simple WinUI3 app, we don't have so much I believe). – Simon Mourier Commented Mar 7 at 10:20
• Are other applications in the RDP session responsive? Is the remote computer doing anything else that limit the resources available for the application? Or does it enter sleep or some other low-power mode that it takes time to recover from? – JonasH Commented Mar 7 at 13:35
• Can you try if this is reproducible on WinAppSDK v1.5.xxx? – Andrew KeepCoding Commented Mar 7 at 21:44
• @AndrewKeepCoding This doesn't appear to be happening with WinAppSdk 1.5 which is interesting. I will need some additional time to verify where exactly it falls over and provide more details later. Good thought :) – Joost Jens Commented Mar 11 at 10:50
• @JonasH Nothing else is running on the remote PC. It's replicatlable both in release builds and in debugger build, with or without a debugger attached. – Joost Jens Commented Mar 11 at 10:51

 |  Show 4 more comments

1 Answer 1

Sorted by: Reset to default 0

It turns out this is a bug in WindowsAppSdk as mentioned by @Domo and @AndrewKeepCoding.

A link to the existing bug report can be found here: https://github/microsoft/microsoft-ui-xaml/issues/10009

Reverting to WindowsAppSdk 1.5 seems to solve the issue though.