-
DescriptionThe problem is very strange for me, I have never encountered this before, and, to be honest, I am not entirely sure what exactly the problem is, in my code, in Avalonia, in .NET Core, or maybe in the debugger. Or maybe not a problem at all, but an inevitable behavior when using a debugger and breakpoints. When I add my custom control to Window (this control uses Render), and then execute an asynchronous command in the WindowViewModel that awaits something longer than ~2 seconds (and has a breakpoint on it), and after that it also executes some code, then when the code of this command is completed, the application freezes completely and then crashes. Steps to reproduce the behavior
When the program crashes, the IDE also displays the following message: Environment
Additional contextThe problem does not arise in production if the program is executed without debugging. The problem also does not arise even if the program is launched in debugging mode but there is no breakpoint on await. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
please ask questions like this using discussions for Telegram first. If it points out it is an issue, we can still open one, okay? |
Beta Was this translation helpful? Give feedback.
-
Hey folks, we have now a sample for it 🎉 |
Beta Was this translation helpful? Give feedback.
I tried changing ReactiveCommand to ICommand, and using the latest Avalonia nightly build, but it didn't help.
All that has changed is the stacktrace: