For the benefit of others, I think I have gotten to the bottom of this.
Looking at the class below, if you remove the lock statements, this will
cause hard crashes throughout the app. Neither monotouch nor xcode will
provide a stack trace in this case. When Spinner.Show() is called before (on
previous screen for example) Spinner.Hide() didn't finish, everything will
blow up.
public class SpinnerHelper
{
private string _title;
public const string DEFAULT_TITLE = "Loading Data. Please
Wait";
private UIAlertView _alert;
private System.Object lockThis = new System.Object();
private const string _title = "Loading, please wait";
public void Show ()
{
lock (lockThis)
{
if (_alert == null)
{
_alert = new UIAlertView (_title, "",
null, null, null);
}
_alert.Show ();
}
}
public void Hide ()
{
lock (lockThis)
{
_alert.DismissWithClickedButtonIndex (0, true);
_alert.Dispose ();
_alert = null;
}
}
}
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/MonoTouch-crashes-with-no-stack-trace-or-crash-report-both-Sim-and-Device-tp4657886p4657889.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
