[mono-android] Simple project with massive memory leak

[Axel Busch]

On 27.11.11 12:53, Jonathan Pryor wrote:
> Do you remember at what count it was crashing at for you?
>
> If I modify the sample to perform a GC.Collect() after the `client.Dispose()` call (Activity1.cs:66), then memory use seems far more stable, staying at ~33.5MB by the same 520 iteration count as above.
Hi Jon. I don't remember how high the count went. If you think it's 
valuable at this time, I can run the code on a few different devices and 
android versions.

I tried GC.Collect() too, with the same result as you're describing. 
Actually I tried quite a few variations and different approaches pretty 
much to the same effect. So I think Jack hit the nail on the head.

I'm glad that this is being addressed, I decided against Android SDK 
because it doesn't fit my workflow, and then decided for m4a instead of 
titanium because of memory issues with the latter. I was beginning to 
wonder whether it was the right decision.

cheers, Axel