Bug 1602 - LIST<> fatal error on iPhone w/ iOS5 but not iPad
Summary: LIST<> fatal error on iPhone w/ iOS5 but not iPad
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-10-20 08:35 UTC by Christopher Keane
Modified: 2013-06-02 12:55 UTC (History)
2 users (show)

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:

Comment 1 Sebastien Pouliot 2011-10-20 14:58:30 UTC
The stacktrace points to MonoTouch_Disposer.Drain (managed) and NSAutoreleasePool release] (native). So I strongly suspect that the issue is not related to the above code (which is not using NSObject and objectiveC references).

Could you attach the "crash dump" (you can get it from XCode) to the bug report ? That will show us every thread (not just the one who crashed). Maybe that will give us some hints. Otherwise we'll likely need a test case (or your application) to pinpoint the issue.
Comment 3 Sebastien Pouliot 2011-10-21 08:46:49 UTC
Thanks for the crash report.

Thread #0 is where the crash occurs but the List<> code you're running looks like it executes on Thread #8. So your problem is not related to code you pasted on the original bug's description.

Something else is occuring on that thread and we'll need more information (e.g. a test case to duplicate the issue or access to your application*) to debug this.

* you can contact support@xamarin.com to get NDA paperwork (if required)
Comment 8 Sebastien Pouliot 2013-06-02 12:55:57 UTC
Please re-open if you still have similar issues and include a test case that will allow us to reproduce the issue.