Replies: 1 comment
-
I know this isn't helpful, but I have been running into this exception with WPF applications out in the wild for 10 years now, since I first developed WPF apps in .NET 4.0 to now in .NET 4.8. It mostly seems to happen when users are running the application for long periods of time (5+ days). Frankly, I think this is something that is unfixable without a major overhaul of the underlying architecture of WPF itself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am diagnosing the WPF render thread failure (WPF app TargetFramework net6.0-windows). In accordance with this documentation related to the issue I am trying to gather any diagnostic info I can. The stacktrace when the app crashes is:
Additional info gathered while running the app under Windbg:
My question relates to the failure to load OLEAUT32.dll - is this something I sould pursue? Will I add to my grief if I try to register this dll on my machine? I have done a fair amount of research on this but most of the related issues are over my head. This is a production app. Any feedback or direction will be greatly appreciated.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions