Blazor WASM AOT Compilation Failure

[ChristopherHaas]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Hi,

We have a problem with Blazor WASM AOT compilation that I cannot seem to diagnose. From dotnet publish, I get the error:
C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\10.0.10\Sdk\WasmApp.Common.targets(672,5): Error : Precompiling failed for G:\source\xxxx\src\xxxx\obj\Release\net10.0\wasm\for-publish\aot-in\xxxxx.dll with exit code -1073741571.

The same error appears when building on our Azure DevOps Linux-based agents.

The build output includes the mono-aot-cross.exe command that failed. When I run that command directly, I end up with:

Failed to load method 0x600014e from 'G:\source\xxxx\src\xxxxx\bin\Release\net10.0\xxxxx.dll' due to Could not resolve type with token 0100001f from typeref (expected class 'System.Collections.Generic.Dictionary`2' in assembly 'System.Collections, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') assembly:System.Collections, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a type:System.Collections.Generic.Dictionary`2 member:(null).

The xxxx.dll is a custom .NET 10 library. I am not sure what triggers this problem. How do I find which method 0x600014e is, and what type 0100001f is?

The .NET version mentioned here is the current insider preview, but the same issue occurs on the latest stable.

Expected Behavior

Successful compilation, or a more detailed error message pointing to the problem.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

10.0.400-preview.0.26322.102

Anything else?

No response

[pavelsavara]

@ChristopherHaas we need minimal repro, currently this is not actionable.

How do I find which method 0x600014e is, and what type 0100001f is?

ildasm MyAssembly.dll /text /tokens > output.il
findstr /i "06000042" output.il

Does it happen randomly or deterministically ?
What's interesting about the failing method ? What data types does it use ?
Does the compiler have enough memory and disk space ?

[ChristopherHaas]

Thank you very much for responding @pavelsavara. I am no longer able to reproduce the error by manually invoking mono-aot-cross.exe with the arguments provided in the build output after updating to v10.0.11. When I run the command directly, it succeeds without errors. However, running dotnet publish, or publishing from VS, still gives the same error. I.e.

C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.WebAssembly.Sdk\10.0.11\Sdk\WasmApp.Common.targets(672,5): Error : Precompiling failed for G:\source\Unison\src\xxxxxx\obj\Release\net10.0\wasm\for-publish\aot-in\xxxx.dll with exit code -1073741571.

I have checked disk space and memory as suggested, and there is plenty of headroom. Do you have any suggestions for how I can diagnose this problem further?

[ChristopherHaas]

With some inspiration from seemingly similar issues (#61053, shimat/opencvsharp_blazor_sample#8), I have tried running publish with following switches:

dotnet publish -c Release -bl -p:DisableParallelAOT=true -p:WasmAllowUndefinedSymbols=true -p:WasmNativeDebugSymbols=false -p:WasmEnableExceptionHandling=false -p:WasmEnableSIMD=false
Unfortunately the AOT build error is the same.