07-11-2025, 12:42 PM
The updated version of DXEngine that was sent to ohmyizzy reduced the number of crashes. However, because the rendering thread in WPF runs on its own thread, it was still possible that after the monitor change occurred, the code in the WPF's render thread was executed before the code in DXEngine. This still caused the application to crash.
The final solution was to solve that in the WPF code.
The code for that was already available, but was waiting for the approval of one of the WPF developers.
See: https://github.com/dotnet/wpf/pull/10394...3009691320
Because nothing was going on with this item and PR, I decided to push that a little bit by writing to the .Net developer community: https://developercommunity.visualstudio....m/10931427
It seem that this helped, because today this WPF fix was approved and merged.
Hopefully the next WPF update will solve this monitor issue.
The final solution was to solve that in the WPF code.
The code for that was already available, but was waiting for the approval of one of the WPF developers.
See: https://github.com/dotnet/wpf/pull/10394...3009691320
Because nothing was going on with this item and PR, I decided to push that a little bit by writing to the .Net developer community: https://developercommunity.visualstudio....m/10931427
It seem that this helped, because today this WPF fix was approved and merged.
Hopefully the next WPF update will solve this monitor issue.
Andrej Benedik