Bug 14326 - GC_start_routine errors
Summary: GC_start_routine errors
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 6.4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-08-29 11:03 UTC by Neal
Modified: 2013-09-24 17:42 UTC (History)
3 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:

Description Neal 2013-08-29 11:03:29 UTC

I use crashlytics and my app is using 6.4.3 and Mono 3.2.0 in the App Store (production).  I'm getting crashlytics errors for "GC_start_routine" in the DidEnterBackground event.  I am running a background task so I'm not sure if that's contributing to this but it shouldn't, but it appears maybe the GC is trying to do a collect in the DidEnterBackground and it's crashing?

Comment 1 Sebastien Pouliot 2013-09-04 14:21:49 UTC
Please attach the crash log or (better) a test case that can be used to reproduce the issue.
Comment 2 Neal 2013-09-10 11:12:26 UTC

See if this can help you see what's going on:

Comment 3 Rolf Bjarne Kvinge [MSFT] 2013-09-24 17:42:13 UTC
GC_start_routine is just the entry point for a thread mono has started (so it'll show up on most of the threads).

The important thread is #5 - exit is called here. Xamarin.iOS has not been thoroughly tested when the process is exiting (because it is very rare that an app actually exits), so we've historically had a few crashes at exit time (which you would never see, because the app was exiting anyway).

Now the frame above the call to 'exit' is 'mono_internal_thread_unhandled_exception' - and that indicates that an exception occurred, and that no catch handler was found for that exception, in which case we'll abort the process. The crash report doesn't contain any information about managed exceptions, so it's impossible to say what happened in this case.

However you might be able to listen on the AppDomain.UnhandledException event and log more information about this when it occurs, so the next time you'll have more information.