-
Notifications
You must be signed in to change notification settings - Fork 698
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
System.TypeLoadException: 'Unable to find a type named 'TrackerCollection<T'' in WinUI3 preview4 #4240
Comments
@Scottj1s and @stevenbrix based purely on the function name I'm guessing this is CSWinrt? |
This issue is affecting the VisualTreeHelper.FindElementsInHostCoordinates and VisualTreeHelper.GetParent methods slowing down the performance every time the ui receives feedback. |
This issue is showing up in XamlControlsGallery, when you try to access changes colors on some controls and when you try to navigate to certain controls pages. I can provide repro steps if need be. |
Do you still see this issue on Project Reunion 0.5.5? This picked up a new CsWinRT, and so far I'm not seeing this problem when playing around in WinUI 3 Controls Gallery. |
Yes, it´s still in Project Reunion 0.5.5 |
Thanks for checking. Do you have more info on how to repro? |
Unfortunately I just installed Net6 sdk, and WinUI 3 stopped working, but you should be able to easily reproduce the problem by calling VisualTreeHelper.GetParent method |
I could create a repo sample
With the following code behind
Enable seeing the handled exceptions Run the app and click everywhere |
Thanks, that repros for me! (And, sorry, I missed your earlier comment about that VisualTreeHelper method hitting this issue.) |
This is a known issue in the Windows OS, and is not likely to be addressed until later this year. The issue is due to an erroneous return string from a system Windows Runtime component's IInspectable::GetRuntimeClassName(). The C#/WinRT runtime attempts to resolve this string to a type, which fails with the given exception. |
Rather than waiting that long for a Windows OS fix, I've added caching to C#/WinRT to prevent the exception storm: I expect this fix will be available in the next public release of C#/WinRT - early May. |
For what it's worth, I randomly started seeing this (in the new caching-enabled codepath) with Project Reunion 0.8 on Windows 10 18363 completely out of the blue (as in, the same code was running under a debugger just fine yesterday). Since it's the same codepath each time, I'm assuming it's the same In case this isn't a "known issue, nothing we can do about it" as of the latest release, here's the stacktrace:
|
I'm constantly seeing the following exception
When enabling "Common Language Runtime Exceptions"
Despite the exception is internal it looks like a bug
The text was updated successfully, but these errors were encountered: