We are still trying to create a test application that demonstrates this problem, and we are burning a lot of man hours doing so. The only clue we've come up with so far is that the crash is more likely when the "GC cleanup summary" numbers get very high (over 200). In our test apps, we can't get that number over ~10. No matter what we do, we can't seem to get that number to go up in the test application.
We aren't absolutely sure that is the root of the problem, but it seems the only real clue we've found so far. What's the best way to get those cleanup numbers to climb? It's starting to turn into a pretty desperate circumstance with this issue. It's completely killing our application, and we've no way of perusing a solution because of the complete lack of call stack or any useful logging. -Aaron On Tue, Dec 13, 2011 at 3:00 PM, chris@Terrago <cdr...@terragotech.com>wrote: > Same for me, 4.0.1 did not fix the issue. I have a sample application that > I > am hoping to expand to show the problem. If it does I'll let you know. > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/Thread-Exceptions-Without-Stacktrace-tp5069711p5072922.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 >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
