Skip to content

Re-enable Release AOT by excluding only OpenCvSharp.dll #9

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.

Sign up for GitHub

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

Merged
shimat merged 3 commits into from
Jul 11, 2026
Merged

Re-enable Release AOT by excluding only OpenCvSharp.dll #9

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e5fc582
Experiment: exclude only OpenCvSharp.dll from AOT to dodge the mono-a…
Jul 11, 2026
282d503
Re-enable AOT for Release, excluding only OpenCvSharp.dll
Jul 11, 2026
8efd32c
Drop the temporary branch trigger now that AOT-on is verified end to end
Jul 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 27 additions & 4 deletions BlazorApp/BlazorApp.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,7 @@
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
<!-- AOT-compiling OpenCvSharp.dll currently crashes mono-aot-cross with a native GC assertion
(sgen-alloc.c:409) on the current wasm-tools workload, on both net8.0 and net10.0. Leave
AOT off for Release until that's fixed upstream; pass -p:RunAOTCompilation=true to retry. -->
<RunAOTCompilation>False</RunAOTCompilation>
<RunAOTCompilation>True</RunAOTCompilation>
</PropertyGroup>

<ItemGroup>
Expand Down Expand Up @@ -69,4 +66,30 @@
<WasmOptConfigurationFlags Include="--enable-threads" />
</ItemGroup>

<!--
Workaround: AOT-compiling OpenCvSharp.dll crashes mono-aot-cross (sgen-alloc.c:409) once its
P/Invoke surface is large (~3100 LibraryImport declarations) - confirmed via a minimal repro
that this is unrelated to native lib size or NativeFileReference itself (see
shimat/opencvsharp_blazor_sample issue 8). The actual OpenCV computation happens in native
C++ regardless of whether this thin C# marshalling layer is AOT'd or interpreted, so
excluding just this one assembly from AOT (it still ships as plain IL, executed by the
interpreter) dodges the crash while the rest of the app still gets AOT'd. This shadows the
SDK's internal "_WasmAotCompileApp" target, so its name/shape may change between SDK versions
- if a future SDK update breaks this, fall back to <RunAOTCompilation>False</RunAOTCompilation>
for Release.
-->
<Target Name="ExcludeOpenCvSharpFromAOT" BeforeTargets="_WasmAotCompileApp" Condition="'$(_WasmShouldAOT)' == 'true'">
<ItemGroup>
<_OpenCvSharpAssemblyToSkipAOT Include="@(_WasmAssembliesInternal)" Condition="'%(FileName)' == 'OpenCvSharp'" />
<_WasmAssembliesInternal Remove="@(_OpenCvSharpAssemblyToSkipAOT)" />
</ItemGroup>
<Message Importance="High" Text="Excluding from AOT: @(_OpenCvSharpAssemblyToSkipAOT)" />
</Target>

<Target Name="ReAddOpenCvSharpAfterAOT" AfterTargets="_WasmAotCompileApp" Condition="'$(_WasmShouldAOT)' == 'true'">
<ItemGroup>
<_WasmAssembliesInternal Include="@(_OpenCvSharpAssemblyToSkipAOT)" />
</ItemGroup>
</Target>

</Project>