[wasm] Blazor/AOT crashing with preview1 - Assertion at /__w/1/s/src/mono/mono/mini/aot-runtime.c:2443
#82481
Labels
Milestone
Comments
ghost
added
the
e012345678
changed the title
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionI am getting the following error after updating my solution to dotnet 8 Preview 1. No compilation config was changed from dotnet 7 to dotnet 8. Reproduction StepsPublish a dotnet 8 Preview 1 Blazor WebAssembly application with Expected behaviorRuntime loads successfully. Actual behaviorSee errors above, program fails. Regression?No response Known WorkaroundsNo response Configurationdotnet.8.0.0-preview.1.23110.8 Other informationNo response
|
radical
changed the title
Assertion at /__w/1/s/src/mono/mono/mini/aot-runtime.c:2443
|
Could you build with |
|
@vargaz See below for build with WasmNativeStrip set to false |
|
Adding |
marek-safar
removed
the
untriaged
|
@vargaz Compiling with |
|
It's safe to use, its just makes the app bigger. This issue will be fixed so the workaround is not going to be required. |
|
@radical we should land a workaround for this in p2 and pick a different default for dedup for blazor targets |
radical
added a commit
to radical/runtime
that referenced
this issue
Mar 1, 2023
radical
added a commit
that referenced
this issue
Mar 2, 2023
…or AOT (#82748) * [wasm] Wasm.Build.Tests: Add blazor+aot run test * cleanup * [wasm] Wasm.Build.Tests: Use $(_IsPublishing) to avoid unncessary .. relinking during "Build", when publishing. `Publish` target triggers `Build` target to run. When publishing, we don't want to run relinking step during the `Build`, as it will be run for `Publish` anyway. Earlier there wasn't a good way to differentiate the two cases of `build` when building, and `build` when publishing, but now the sdk sets `$(_IsPublishing)=true`, which can be used here. * fix blazor tests * Wasm.Build.Tests: Add support for running published blazor projects `dotnet run` uses the regular build output. Published blazor app, like when using AOT, needs to be run more "manually" by starting a web server in the publish folder. This is accomplished here by using the new xharness command `wasm webserver`. * Detect runtime assertions in blazor runs * Update test to track changes * cleanup * Disable BlazorPublishRunTest because of #82481 * Update test to track changes * Update xharness dependency Updating 'Microsoft.DotNet.XHarness.CLI': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness') Updating 'Microsoft.DotNet.XHarness.TestRunners.Common': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness') Updating 'Microsoft.DotNet.XHarness.TestRunners.Xunit': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness')
|
Is this fixed in the .net 8 preview 2 released yesterday? |
|
Seems not. It doesn't work without the WasmDedup setting in .net 8 Preview 2. |
|
What is the current error message ? |
|
|
Could you run with false ? Also, the stack trace is a bit hard to read, but this appears to be a different error. |
|
Probably a different error yeah. I am currently unable to run with false settings because we've rolled back everything to .NET 7 already. The settings we had were: We tried both with |
radical
added a commit
to radical/runtime
that referenced
this issue
Jun 20, 2023
`Blazor.BuildPublishTests.WithDllImportInMainAssembly` `Blazor.BuildPublishTests.BlazorPublishRun` Issue: dotnet#82725 Issue: dotnet#82481
radical
added a commit
that referenced
this issue
Jun 21, 2023
* [wasm] Use -s EXPORT_ES6=1 only for link time Fixes `emcc: warning: linker setting ignored during compilation: 'EXPORT_ES6' [-Wunused-command-line-argument]` * [wasm] Fix loading `dotnet.native.js.symbols` * [wasm] WBT: Re-enable skiasharp test .. as a new build of skiasharp native lib is now available. Fixes issue: #82725 * [wasm] WBT: Enable more previously disabled tests `Blazor.BuildPublishTests.WithDllImportInMainAssembly` `Blazor.BuildPublishTests.BlazorPublishRun` Issue: #82725 Issue: #82481 * [wasm] Browser.targets - fix up paths for webcil * [wasm] Add make target build-packages to build the nugets * address review feedback from @maraf, and add text implementations for node, and error cases * address review feedback from @maraf * WBT: remove unnecessary code WithDllImportInMainAssembly: remove `CheckNativeFileLinked` because we can run the blazor project now. * address review feedback from @pavelsavara * Disable failing blazor test on windows
|
Haven't seen this in quite some time considering it closed |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I am getting the following error after updating my solution to dotnet 8 Preview 1. No compilation config was changed from dotnet 7 to dotnet 8.
Reproduction Steps
Publish a dotnet 8 Preview 1 Blazor WebAssembly application with
Expected behavior
Runtime loads successfully.
Actual behavior
See errors above, program fails.
Regression?
No response
Known Workarounds
No response
Configuration
dotnet.8.0.0-preview.1.23110.8
Windows 10 x64
Chrome
Other information
No response
The text was updated successfully, but these errors were encountered: