Bug 13484 - Assertion at mini/aot-runtime.c:426, condition `gclass->generic_container' not met
Summary: Assertion at mini/aot-runtime.c:426, condition `gclass->generic_container' no...
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 6.4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-25 15:47 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2013-08-23 20:35 UTC (History)
7 users (show)

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

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 FIXED

Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2013-07-25 15:49:07 UTC
Reported on behalf of a user:

After upgrading MonoTouch and Xamarin Studio and resolving all build errors I
am now unable to debug on the device without the application crashing.
-Debug in simulator works without an issue so far
-Application built for release runs on the iOS device without issue so far
-Attempting to debug the application on the device results in an exception
-I restarted both the device and my computer, and the issue persists
-I discovered a work around. The error goes away if I do a full rebuild of the
solution. The error did return again, but a rebuild continues to fix the
problem for a short while.


Here is the version information and the contents of the device log at the time
the application crashed:

=== Xamarin Studio ===

Version 4.0.10 (build 7)
Runtime:
Mono 3.2.0 ((no/7c7fcc7)
GTK 2.24.20
GTK# (2.12.0.0)
Package version: 302000000

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.Android ===

Version: 4.8.0 (Enterprise Edition)
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
Java SDK: /usr
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)

=== Xamarin.iOS ===

Version: 6.4.0.2 (Enterprise Edition)
Hash: c9f7659
Branch:
Build date: 2013-18-07 21:36:03-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Build Information ===

Release ID: 400100007
Git revision: f324e2154ee86ae1b6b8483392eddbf418e6381b
Build date: 2013-07-20 06:23:58+0000
Xamarin addins: fe4f180e2386eafc00087ef68c3a580cff4a2592

=== Operating System ===

Mac OS X 10.8.4
Darwin local 12.4.0 Darwin Kernel Version 12.4.0


Jul 25 13:35:40 iPhoneiRConnect[155] <Critical>: * Assertion at
../../../../../mono/mono/mini/aot-runtime.c:426, condition
`gclass->generic_container' not met
Jul 25 13:35:40 iPhoneiRConnect[155] <Error>: Stacktrace:
Jul 25 13:35:40 iPhoneiRConnect[155] <Error>: at <unknown> <0xffffffff>
Jul 25 13:35:40 iPhoneiRConnect[155] <Error>: at
RCBusinessLib.Data.DataNode.get_AncestorsAndSelf () [0x000ec] in
/Users/Projects/iRConnect_Mono_Sync/Shared/RCBusinessLib/Data/DataNode.cs:403
--snip--
Comment 3 Rolf Bjarne Kvinge [MSFT] 2013-07-29 12:00:49 UTC
Could you please attach a test case/project?
Comment 5 Eduardo Coelho 2013-08-02 11:28:24 UTC
I'm having the same issue here
```
<Critical>: * Assertion at ../../../../../mono/mono/mini/aot-runtime.c:426, condition `gclass->generic_container' not met
```

I'm able to run the application successfully:
- in the Simulator in both Release/Debug modes
- in the Device in the Debug mode

However the application always crashes in the Device when build with Release (I found that in the hard way - after all my ad-hoc installation reported the failure).

The workaround suggested by Brendan Zagaeski did the tricky, a full rebuilt allowed me to run the application in Release mode @ Device.
Comment 6 Mark Foley 2013-08-05 04:09:29 UTC
Yes, I have the same issue.  It was seeming very intermittent, but indeed it seems to be about whether you've done a full rebuild (it works) or are running again after changes (it crashes on startup).

I had spent a long time enabling/disabling generic sharing, llvm and so forth but that isn't it.

Is there an EST on when a fix might appear in alpha?  I'm in the stable channel now.
Comment 7 Rolf Bjarne Kvinge [MSFT] 2013-08-05 05:17:38 UTC
Mark, a fix will likely appear in alpha soon after we figure out what the bug actually is. Would it be possible to get access to your project so that I can try to reproduce this myself?
Comment 8 Mark Foley 2013-08-05 21:11:17 UTC
Hi Rolf, thanks for that.  I have what might be good news... I was just sitting down to try and cut the project down to send it to you, and it appears to be resolved (for my project at least) as of the hotfix just released!  It might be worth asking the other posters if theirs is resolved also, and then it could be closed.

Many thanks Rolf.
Comment 9 David Jade 2013-08-16 03:29:53 UTC
I too just started seeing this with an AdHoc build. The app in question works fine in the simulator, fine on my iPhone with debug and release development builds but I just created an AdHoc build, uploaded to TestFlight and installed it OTA to my iPad (which has never been used for development so no profiles, etc..). In this scenario it updated over the previous App Store installed version. Now when I launch the app I get this crash and error in the console.

For me though, if I try to restart it over and over sometimes it will launch sometimes. Other times even though it has died I still need to force-kill it from the running apps and then sometimes it will then launch. Crashing at start up seem really random to me, probably 75% of the time. All I ever see before it crashes is the static splash screen.

However, forcing a complete rebuild and re-installing from TestFlight seems to have fixed it for me.

I have never seen this error before with development builds deployed to my iPhone, either incremental or full rebuilds.

Xcode 4.6.3, Xamarin stable
Comment 10 Dan Abramov 2013-08-22 11:37:45 UTC
I have exactly the same issue.
It doesn't happen every time, and when it does, cleaning and rebuilding seems to work.

=== Xamarin Studio ===

Version 4.0.12 (build 3)
Installation UUID: a12ea7ee-6056-4ee5-80fb-b38d90b05195
Runtime:
	Mono 3.2.0 ((no/7c7fcc7)
	GTK 2.24.20
	GTK# (2.12.0.0)
	Package version: 302000000

=== Apple Developer Tools ===

Xcode 4.6.2 (2067.2)
Build 4H1003

=== Xamarin.iOS ===

Version: 6.4.3.0 (Business Edition)
Hash: 0068990
Branch: 
Build date: 2013-13-08 05:24:39-0400

=== Xamarin.Android ===

Not Installed

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Build Information ===

Release ID: 400120003
Git revision: 593d7acb1cb78ceeeb482d5133cf1fe514467e39
Build date: 2013-08-07 20:30:53+0000
Xamarin addins: 25a0858b281923e666b09259ad4746b774e0a873

=== Operating System ===

Mac OS X 10.9.0
Darwin Dan.local 13.0.0 Darwin Kernel Version 13.0.0
    Tue Jul 30 20:52:22 PDT 2013
    root:xnu-2422.1.53~3/RELEASE_X86_64 x86_64
Comment 11 Rolf Bjarne Kvinge [MSFT] 2013-08-22 11:48:35 UTC
Dan: can you provide a test project we can use to reproduce the issue?
Comment 12 Brendan Zagaeski (Xamarin Team, assistant) 2013-08-22 11:59:48 UTC
David and Dan, in case it's helpful, note that you can mark attachments to this bug report as private too so that only the Xamarin Team can see them.
Comment 14 Rolf Bjarne Kvinge [MSFT] 2013-08-23 20:35:17 UTC
Dan's issue has been fixed in the upcoming 6.4.4 release, so I'm closing this bug report since it's likely this issue has been fixed.

If anyone can still reproduce it once 6.4.4 has been released, please reopen this bug report and attach a project we can use to reproduce the crash ourselves.