Skip to content
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

AOT compile aot-instances.dll, the AOT compiler exited with code 139. #109966

Open
rolfbjarne opened this issue Nov 19, 2024 · 14 comments
Open

AOT compile aot-instances.dll, the AOT compiler exited with code 139. #109966

rolfbjarne opened this issue Nov 19, 2024 · 14 comments
Assignees

Comments

@rolfbjarne
Copy link
Member

From @bwinklesky on Fri, 15 Nov 2024 19:19:59 GMT

Apple platform

iOS

Framework version

net9.0-*

Affected platform version

.NET 9

Description

After upgrading to Xcode 16 and upgrading source code to version 9 we are getting this error.

IL stripping assemblies
12:01:24 Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/9.0.0/Sdk/../tools/mono-aot-cross execution finished (exit code = 139).
12:01:24
12:01:24 /usr/local/share/dotnet/packs/Microsoft.iOS.Sdk.net9.0_18.0/18.0.9617/targets/Xamarin.Shared.Sdk.targets(1277,3): error : Failed to AOT compile aot-instances.dll, the AOT compiler exited with code 139.

Steps to Reproduce

dotnet publish release

Did you find any workaround?

No response

Build logs

No response

Copied from original issue xamarin/xamarin-macios#21634

@rolfbjarne
Copy link
Member Author

From @rolfbjarne on Fri, 15 Nov 2024 19:29:01 GMT

Could you get an MSBuild binlog and attach it here? Thanks!

@rolfbjarne
Copy link
Member Author

From @bwinklesky on Fri, 15 Nov 2024 19:52:13 GMT

msbuild.binlog.zip

Let me know if this doesn't work

@rolfbjarne
Copy link
Member Author

From @rolfbjarne on Mon, 18 Nov 2024 08:13:11 GMT

Unfortunately that didn't give me many clues.

Is there any chance we could get access to your project to compile it ourselves?

@rolfbjarne
Copy link
Member Author

From @bwinklesky on Mon, 18 Nov 2024 19:06:13 GMT

Unfortunately that didn't give me many clues.

Is there any chance we could get access to your project to compile it ourselves?

@rolfbjarne I created a respository and gave you access. WasatchBackcountryAlliance is the app to build.

I ask that you destroy the source code after you've diagnosed the issue.

@rolfbjarne
Copy link
Member Author

From @rolfbjarne on Tue, 19 Nov 2024 12:28:31 GMT

Unfortunately that didn't give me many clues.
Is there any chance we could get access to your project to compile it ourselves?

@rolfbjarne I created a respository and gave you access. WasatchBackcountryAlliance is the app to build.

I ask that you destroy the source code after you've diagnosed the issue.

I confirm I can reproduce the problem; I'll see if I can figure out where to route the bug and create a smaller test project that doesn't involve any of your code.

@rolfbjarne
Copy link
Member Author

From @formerlymisterhenson on Tue, 19 Nov 2024 13:27:19 GMT

Well this error occured in my project as well, I went with:

<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Release|net9.0-ios|AnyCPU'">
    <EnableSGenConc>True</EnableSGenConc>
    <MtouchInterpreter>-all,System.Private.Windows.Core</MtouchInterpreter>
</PropertyGroup>

@rolfbjarne
Copy link
Member Author

From @rolfbjarne on Tue, 19 Nov 2024 16:17:20 GMT

Smaller test case: aot-instances-1003365.zip

To repro: unzip & run ./bug.sh

Binlog: msbuild.binlog.zip

Crash report (mono-aot-cross): crash.txt

@bwinklesky
Copy link

From @rolfbjarne on Tue, 19 Nov 2024 12:28:31 GMT

Unfortunately that didn't give me many clues.
Is there any chance we could get access to your project to compile it ourselves?

@rolfbjarne I created a respository and gave you access. WasatchBackcountryAlliance is the app to build.
I ask that you destroy the source code after you've diagnosed the issue.

I confirm I can reproduce the problem; I'll see if I can figure out where to route the bug and create a smaller test project that doesn't involve any of your code.

@rolfbjarne thanks for looking into this!

@mwilson25
Copy link

Just to let you know that I have this problem also - exactly as described above. I gave the solution from @formerlymisterhenson a shot and my build has now completed OK. However, not sure whether

True
-all,System.Private.Windows.Core

is going to have any adverse effects?

@ivanpovazan ivanpovazan added os-ios Apple iOS and removed untriaged New issue has not been triaged by the area owner labels Nov 21, 2024
Copy link
Contributor

Tagging subscribers to 'os-ios': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

@vitek-karas
Copy link
Member

@BrzVlad could you please repro from Rolf's repro and get a real callstack - the one in the crash report is probably without symbols. That should help us triage this better.

@GUELIANEBelkacem
Copy link

Any news on this issue? we have the exact same

@BrzVlad
Copy link
Member

BrzVlad commented Dec 9, 2024

The fix is there, the release cycle will take a while. I would assume the new .NET9 version will be available sometime in January.

@vitek-karas
Copy link
Member

The backport to 9 is #110271.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants