-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UCEERR_RENDERTHREADFAILURE when hosting ElementHost within WindowsFormsHost #3719
Comments
The stack trace is all WPF, so transferring there until it can be established the issue is in our code. |
Is there anything new regarding this ticket? |
Hi this is still an issue are there any updates on this? |
@julian-di Do you find the repro? |
@lindexi, what do you mean with repro? |
Are there any news on this? |
Are there any updates on this issue / underlaying problem ? Any approach how the bug can be solved or prevented ? |
.NET Core Version:
Did not find a quick way doing this in .net core
Have you experienced this same bug with .NET Framework?:
Yes
.net 4.8
Problem description:
I have a hybrid WinForms/WPF (so I'm not sure if its a WinForms or WPF issue) application with an ElementHost. The child element is a WPF UserControl with a TabControl. Via the ItemsSource different types of tabs are displayed.
The third case seems pretty crazy and stupid, but is the case.
Switching between the tabs, the application crashes pretty fast with 2 exceptions.
1st UCEERR_RENDERTHREADFAILURE System.Windows.Media.Composition.DUCE+Channel.SyncFlush
2nd FATAL_USER_CALLBACK_EXCEPTION An unhandled exception was encountered during a user callback.
Expected behavior:
The render thread failure is not random and always renders on the correct thread.
Minimal repro:
https://github.com/AndreasBreuninger/ElementHost_RenderError
CrashDumps included.
Related issues
These issues seem to be related, but still different. They all rely on the HostVisual element.
wpf/128
wpf/3100
wpf/3567
Also checked the release notes of kb4562900-cumulative-update-for-net-framework
The text was updated successfully, but these errors were encountered: