Aargh, nightmare.... Thanks for the suggestion.
Sadly, I had to run an automated UI test thread for about half an hour to reproduce it. With gref logging enabled, goodness knows whether I can repeat it before generating enough log output for even nasa to struggle with :) I take it that the stacktrace produced is just the current stack of the app when signalled to terminate by the os and therefore has probably no bearing on the prematurely disposed reference - i.e. it could be anywhere in the UI code and the stacktrace is a bit of a red herring? Cheers Iain -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/jni-error-with-4-2-4-on-jellybean-tp5711456p5711461.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
