----- Original Message ----- > From: Jonathan Pryor <j...@xamarin.com> > To: Discussions related to Mono for Android <monodroid@lists.ximian.com> > Cc: > Sent: Friday, 20 July 2012, 21:41 > Subject: Re: [mono-android] Random crashes > > On Jul 20, 2012, at 8:28 AM, jayemmess wrote: >> I've inherited a project built using Mono for Android and need > establish why it is occasionally crashing. I have no prior experience of > Android or Mono, but am a .net developer. > > Which Mono for Android version? Which target device? Which Android version on > the Target device?
Hi Jon - thanks for all the awesome help. It was actually using MfA 4.0.6 and an EasyPad 730 running 2.3.1. I'm actually in the process of re-factoring the app which includes building with MfA 4.2.4. [...] > That message gives us a pid (479), which greatly narrows down the output: > Lots > of messages from 479 are NameResolutionFailure messages, suggesting that > there's some kind of network issue. A quick sanity check is to see if the > Browser app on your device is able to access the same website that your app > is > trying to access. The device was indeed not connected to a network at that time, though I had also seen the issues when it was connected to the network. > We can also see that the gref count is constantly increasing: > > 07-20 19:36:13.825 D/dalvikvm( 479): GREF has increased to 1301 > > This is usually a sign that the GC isn't running frequently enough, or > you're constantly creating new objects which are referenced by both VMs: > > http://docs.xamarin.com/android/advanced_topics/garbage_collection > http://docs.xamarin.com/android/advanced_topics/diagnostics There seemed to be some problem with the way that navigation was implemented resulting in an ever growing back stack. To address this I'm re-factoring the app to not use MonoCross (almost all the logic in the views anyway) so that I have full control over the navigation. I suspect the problem with the MonoCross navigation was down to my/the previous developers' misunderstandings rather than a fault of the framework but it was adding a level of complexity with little benefit in this instance. Also, it doesn't seem to be kept up to date particularly well and it was causing problems with updating MfA. > This is troubling though: > > 07-20 19:36:22.795 I/mono ( 479): Stacktrace: > 07-20 19:36:22.795 I/mono ( 479): Fingers crossed that goes away with the MfA update then! Thanks again, J _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
