Bug 12561 - SIGSEGV in Simulator causes crash
Summary: SIGSEGV in Simulator causes crash
Alias: None
Product: iOS
Classification: Xamarin
Component: Pre-release ()
Version: 6.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 6.4 (async)
Assignee: Bugzilla
Depends on:
Reported: 2013-06-05 14:45 UTC by Dan Abramov
Modified: 2013-07-12 10:37 UTC (History)
4 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 Dan Abramov 2013-06-05 14:45:09 UTC
Mono 3.0.10 ((no/eff4cb5)
Xamarin iOS (Business Edition)

I just got a SIGSEGV in Simulator with Xamarin.iOS 6.3.6:

mono-rt: Stacktrace:

mono-rt:   at <unknown> <0xffffffff>
mono-rt:   at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <IL 0x0009f, 0xffffffff>
mono-rt:   at MonoTouch.UIKit.UIApplication.Main (string[],string,string) [0x0004c] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:38
mono-rt:   at Stampsy.Application.Main (string[]) [0x00001] in /Users/dan/Documents/Projects/stampsy-ipad/Stampsy/Main.cs:17
mono-rt:   at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff>
Native stacktrace:

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.

Looks similar to #11286, but in this case it's not hanging but just crashing.
Can't reproduce at will though.
Comment 1 Sebastien Pouliot 2013-06-05 15:07:54 UTC
Console.app should have a crash report, could you locate/attach it ?

They are not often useful - but it should have a bit more details than the above stack trace.
Comment 6 PJ 2013-07-09 05:26:29 UTC
Heyo Dan, Zoltan - we're closing in on 6.4 release so any last minute feedback here would be much appreciated. There should be a 6.3.7 build out tomorrow that will closely resemble our RC.
Comment 7 Dan Abramov 2013-07-09 05:28:35 UTC
Hey folks, I'll give it a go today, stay tuned.
Comment 8 Dan Abramov 2013-07-09 07:07:48 UTC
Seems to work pretty stable. No problems so far.
Comment 9 PJ 2013-07-09 15:07:42 UTC
Thank you Dan! I appreciate the testing you're doing today. 

I know that this was not reliably reproducible when first reported, so please feel free to REOPEN if you see it again.
Comment 10 Dan Abramov 2013-07-09 16:48:06 UTC
Sure, thanks for raising the issue.

This bug was the main reason I didn't switch to Alpha.
Now that it seems fixed, I don't need to switch back to Stable immediately.
Comment 11 narayanp 2013-07-12 10:37:29 UTC
Today we have checked this issue with following builds:

X.S 4.0.10
Mono 3.1.1-2

And to reproduce this issue we have run iOS templates and iOS samples on iOS Simulator, All application deployed and launched successfully on Simulator, Simulator not crashed.

Changing the status to Verified.