Open mtbayley opened 3 months ago
I can confirm that the issue is gone when RunAOTCompilation
is false
@mtbayley thanks for contacting us.
This seems like a bug in the AoT process. Do you happen to have a repro project that we can use to troubleshoot this issue? In the meantime I'm going to transfer this to the runtime so they can investigate.
@lewing FYI
Hi @javiercn, @lewing Here's a link to a minimal repro project. It is just the Blazor web app template with RunAOTCompilation set to true
https://github.com/mtbayley/TestAot
I've been able to trigger it on some machines by navigating to the Counter page. Then loading the Weather page. Then going back to the Counter page. Same exception occurs.
Another update: The machines that it fails on are all virtualized. All physical machines I have tested so far have no issues
On the virtualized machines, only chromium based browsers do not work (chrome, edge). Firefox works.
Setting WasmEnableSIMD
to false works around the issue. I can't understand why. SIMD should be supported by all major browsers
Looks similar as https://github.com/dotnet/runtime/issues/96004
@maraf is there any action we can take?
Is there an existing issue for this?
Describe the bug
I can't think of how this is possible, but I get this message on startup of my published AOT compiled Blazor Web App. Some machines have no problem loading the site, but some machines show this error consistently.
Any help on where to look would be appreciated
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
.NET Version
8.0.6
Anything else?
No response