Thanks Jon. Looking at the monodroid-gc logs I often see items like this:
>> 01-18 02:40:13.855: I/monodroid-gc(4606): GC cleanup summary: 29 objects >> tested - resurrecting 0. Most of the time the result is "resurrecting 0". Sometimes I see this: >> 01-18 02:41:34.845: I/monodroid-gc(4606): GC cleanup summary: 141 objects >> tested - resurrecting 34. My knowledge of garbage collection is non-existent; so I hope this question doesn't ruin my rep. I presume that GC is tricky because if it has to be done for memory sake but if it's too aggressive you run into issues. So if a thread is in the middle of deserializing a large object graph - GC shouldn't touch that right? Also is the GC process "timer aware"; presumably it is fairly circumspect about what it marks for cleaning up with respect to thread code in between timer ticks? I'm asking because most of the heavy lifting in my app happens on a system timer thread. -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Mono-crashing-at-System-MonoType-GetProperties-call-tp5152993p5154851.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
