-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
iOS: System.Runtime.Loader.AssemblyLoadContext.MonoResolveUnmanagedDllUsingEvent is linked away when still needed #46908
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @CoffeeFlux Issue DetailsDescriptionThe System.Runtime.Loader.AssemblyLoadContext.MonoResolveUnmanagedDllUsingEvent method is linked away when it's still needed, resulting in an assertion at runtime:
Crash report: link sdk_2021-01-12-235327_XAMBOT-1105-20210112_235328.crash.txt Standard output: stdout-20210112_235311.log The workaround is to preserve the method that is linked away: My guess is that this is a regression caused by #46323. This is with .NET 6.0.100-alpha.1.21060.3 (from yesterday). CC @marek-safar
|
… to work around a bug in .NET 6. Ref: dotnet/runtime#46908.
Tagging subscribers to this area: @CoffeeFlux Issue DetailsDescriptionThe System.Runtime.Loader.AssemblyLoadContext.MonoResolveUnmanagedDllUsingEvent method is linked away when it's still needed, resulting in an assertion at runtime:
Crash report: link sdk_2021-01-12-235327_XAMBOT-1105-20210112_235328.crash.txt Standard output: stdout-20210112_235311.log The workaround is to preserve the method that is linked away: rolfbjarne/xamarin-macios@ece7188 My guess is that this is a regression caused by #46323. This is with .NET 6.0.100-alpha.1.21060.3 (from yesterday). CC @marek-safar
|
Follow up change missing in dotnet#46323 Fixes dotnet#46908
Follow up change missing in dotnet/runtime#46323 Fixes dotnet/runtime#46908
…0743) Follow up change missing in dotnet/runtime#46323 Fixes dotnet/runtime#46908 Co-authored-by: marek-safar <[email protected]>
* Bump to .NET 6.0.100-alpha.1.21060.3. * Fix dotnet command line arguments. * dotnet build: the project file must be the first argument. * dotnet build/publish: use the documented verbosity format. * Update version number in tests. * [tests/introspection] Adjust introspection to cope with different library names in the new .NET version. * [tests/link sdk] Adjust the LinkSdkRegressionTest.SpecialFolder test according to the new version of .NET 6. * [tests/link sdk] Preserve a required method in System.Private.CoreLib to work around a bug in .NET 6. Ref: dotnet/runtime#46908. * Revert "[CI][VSTS] Add the donet 6 pkg as a dependency. (#10348)" This reverts commit 6de4e71. There's no need to provision .NET 6, it's done automatically.
…around a bug in .NET 6. Ref: dotnet/runtime#46908.
…around a bug in .NET 6. (#10426) Ref: dotnet/runtime#46908.
Includes fixes for dotnet/runtime#46908
Description
The System.Runtime.Loader.AssemblyLoadContext.MonoResolveUnmanagedDllUsingEvent method is linked away when it's still needed, resulting in an assertion at runtime:
Crash report: link sdk_2021-01-12-235327_XAMBOT-1105-20210112_235328.crash.txt
Standard output: stdout-20210112_235311.log
The workaround is to preserve the method that is linked away: rolfbjarne/xamarin-macios@ece7188
My guess is that this is a regression caused by #46323.
This is with .NET 6.0.100-alpha.1.21060.3 (from yesterday).
CC @marek-safar
The text was updated successfully, but these errors were encountered: