Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Mono 3.0.10 ((no/eff4cb5)
Xamarin iOS 18.104.22.168 (Business Edition)
I just got a SIGSEGV in Simulator with Xamarin.iOS 6.3.6:
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>
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.
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.
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.
Hey folks, I'll give it a go today, stay tuned.
Seems to work pretty stable. No problems so far.
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.
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.
Today we have checked this issue with following builds:
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.