Xamarin.iOS device builds freeze after Xcode 13.4.1 update #15286
Milestone
Comments
|
I reported this issue through the Visual Studio for Mac feedback tool. After further investigation I have narrowed the issue down, and have published a repository reproducing the problem at https://github.com/follesoe/DeedleBuildIssue. It is a default single view iOS application created using the Visual Studio for Mac 2022 template, where the only changes I have done is:
using System;
using Deedle;
namespace DeedleBuildIssue
{
public class FrameBuilder
{
public FrameBuilder()
{
}
// If I uncomment this method, the build hangs.
/*
public Frame<DateTimeOffset, string> ToFrame()
{
return Frame.CreateEmpty<DateTimeOffset, string>();
}
*/
}
}If I uncomment the method returning It builds just fine for simulator, and it builds fine for device if I remove that method (so it is not related to incorrect provisioning profiles or certificates). I am using the following versions: |
|
A tip from @praeclarum is that the AOT compiler can be quite slow with F# libraries using large amounts of generics, which is also the case for Deedle. So it could be a generic (pun intended) performance issue with AOT of F# code, or Deedle sends the AOT compiler into a path that stalls/never completes? It does not complete in ~60 min on AppCenter build agents (the build gets terminated). |
|
I let it run until completion on my local computer, and got 699 build errors: |
dalexsoto
added
bug
|
I was able to reproduce this bug with the outlined steps I have attached the sample I used and the binlog, that said I used Xcode 13.3 to reproduce this so this is definitely not something because of Xcode 13.4. I used Xamarin.iOS Legacy. I can't attach mtouch-cache folder because the directory itself is 22 GB and the big culprit is deedle.dll.s
TestAppiOS.zip @rolfbjarne would this be on our side or the runtime? This is an F# library so probably this is hitting an edge case in the AOT compiler. Click to expand system info! |
|
@dalexsoto this would be on the runtime side, but two questions come up:
|
@follesoe do you know? |
|
I can definitely repro this with NET 6, that said I left it run it for an hour and it did not finish.
|
|
Moved issue to dotnet/runtime#71333 |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue has been moved from a ticket on Developer Community.
After updating to Xcode 13.4.1 Xamarin.iOS device builds fails on both my macs (running the same version of Xcode, Visual Studio for Mac, and Xamarin.iOS). One of the machines is an Intel mac, while the other is an M1, so same behaviour on both architectures.
After force quiting Visual Studio, I still have one or more orphan arm64-darwin-mono-sgen processes lingering, causing high CPU load.
The problem happens consistently. I can build for Simulator and other project types (such as .NET 6 Unit Test projects) just fine.
Original Comments
Feedback Bot on 6/14/2022, 08:09 PM:
(private comment, text removed)
Jonas Follesø on 6/15/2022, 00:44 AM:
(private comment, text removed)
Jonas Follesø on 6/15/2022, 04:29 AM:
(private comment, text removed)
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: