Bug 43536 - [iOS] MTOUCH: error MT3001: Could not AOT the assembly
Summary: [iOS] MTOUCH: error MT3001: Could not AOT the assembly
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler ()
Version: XI 9.8 (tvOS / C7)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2016-08-19 10:15 UTC by Al Clark [MSFT]
Modified: 2017-02-07 11:56 UTC (History)
9 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Sample and build output (155.25 KB, application/zip)
2016-08-19 10:15 UTC, Al Clark [MSFT]
Details
Image of version and processes (390.30 KB, image/png)
2016-08-19 10:22 UTC, Al Clark [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Al Clark [MSFT] 2016-08-19 10:15:37 UTC
Created attachment 17119 [details]
Sample and build output

== Overview

Building project never completes.  llc process using 100% CPU indefinitely.  Build process completes (fails) after killing this process.

== Steps to reproduce

Load Xamarin Studio for Mac.
Load attached project.
Build project.

== Expected behaviour

Project to build and deploy to device / sim.

== Actual behaviour

Project build halts with process 'llc' using 100% CPU.  Process can be killed and build continues with error:

MTOUCH: error MT3001: Could not AOT the assembly '/Users/DPLabs/Documents/MachiningCloudGit/MachiningCloud/MachiningCloud.UI.Ios/obj/iPhone/Ad-Hoc/mtouch-cache/64/Build/MachiningCloudApp.exe'

*** Sample and Build Output attached ***

== Version information

=== Xamarin Studio Business ===

Version 6.1 (build 4963)
Installation UUID: 51f5ac26-e47e-45a4-8735-cbfa82ca4a6f
Runtime:
	Mono 4.4.0 (mono-4.4.0-branch/fcf7a6d) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000148

=== NuGet ===

Version: 3.4.3.0

=== Xamarin.Profiler ===

Not Installed

=== Xamarin.Android ===

Not Installed

=== Xamarin Android Player ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.3.1 (10188.1)
Build 7D1014

=== Xamarin.iOS ===

Version: 9.9.0.288 (Xamarin Business)
Hash: ef65ca5
Branch: master
Build date: 2016-06-07 21:27:36-0400

=== Xamarin.Mac ===

Not Installed

=== Build Information ===

Release ID: 601004963
Git revision: b37c52e0249c009e308eb144957ac97d1003ec0e
Build date: 2016-06-10 12:00:02-04
Xamarin addins: db4bae9b11a32d16ee009695cd1bfa36455187b0
Build lane: monodevelop-lion-cycle8-preview2

=== Operating System ===

Mac OS X 10.11.5
Darwin DPLabss-Mac-mini.local 15.5.0 Darwin Kernel Version 15.5.0
    Tue Apr 19 18:36:36 PDT 2016
    root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
Comment 1 Al Clark [MSFT] 2016-08-19 10:22:46 UTC
Created attachment 17120 [details]
Image of version and processes
Comment 6 Al Clark [MSFT] 2016-08-30 11:26:23 UTC
Disabling LLVM allows the project to be build (as expected).

Additional information from the customer:

When we were using Xamarin.IOS 9.9.0.288 the llc process gives strange error message:
* Assertion: should not be reached at /Users/builder/data/lanes/1381/ef65ca51/source/xamarin-macios/external/mono/mono/mini/llvm-jit.cpp:753

And the build fails. This happened with our full solution, not the sample.

I have tried the sample on v. 9.99.2.40, it hangs. And on the latest version (9.99.4.23) the sample still hangs.