System.ExecutionEngineException upgrading MaterialDesignThemes from 5.1.0 to 5.2+

[red-things]

Bug explanation

I don't expect this to be able to be addressed by wanted to log this issue in case anyone else sees anything like it. I'm not sure where I should put this and if this isn't the right place please let me know where.

I get a System.ExecutionEngineException after upgrading MaterialDesignThemes from 5.1.0 to 5.2.0/5.2.1 (tried both).
The ONLY thing I change is the MaterialDesignThemes NuGet package version. Both 5.2 or 5.2.1 will result in a System.ExecutionEngineException; reverting to 5.1 avoids the exception and everything works perfectly.

I can reproduce the exception at will with the solution with the exception by upgrading to MaterialDesignThemes 5.2 or 5.2.1; downgrading to 5.1.0 will remove the exception. Nothing else changes. A full cleanup of the environment (bin, obj, and .vs in each project are deleted at the filesystem level and Build Clean Solution) is run before each test, VS exited then the solution re-built before each test.

The exception manifests itself when a specific multi-part page that is constructed from multiple nested user-controls is opened with a particular dataset (not sharable unfortunately). The actual line where the exception is thrown is when sending a property changed event but that doesn't appear to have nothing to do with the problem (all relevant fields and properties are correctly populated and a partial stack trace is available but shows nothing and all data is valid at each step).

Unfortunately this solution has 30+ sub-modules/projects many of which are shared with 2 other solutions. No code was changed and there's no unsafe code in any of the modules being run in this solution: I was simply updating the NuGet packages across all solutions and ran into this exception when testing.

One of the other solutions uses WPF/Material Design and has the same multi-part page and dataset - and of course interestingly it does not throw an exception. So reproducibility is not my strong suit here. All solution are .net8 throughout.

I know this particular exception type is hard to trace and it could full well be that this is in my code somewhere. But it only shows up with MaterialDesignThemes 5.2/5.2.1.

Version

5.2.0/5.2.1