Hi Romain, thanks for answering this post. I think I read all your blog posts according to this subject... Maybe it's clear for you that this behavior is normal but it was at least not clear for me.
I also think that a lot of other people are suffering with that. In all the posts I read it was nowhere mentioned that debugging itself could be the problem. (A bit like quantum physics ;-)) Heap checks are mostly done wile debugging - isn't it. So the heap goes up but never down. Next step is MAT. Now, if MAT shows a problem (specially such a problem with references back to the activity) you can't be sure if it's really a problem or not? Means also never thrust MAT while debugging - is this the message? thx Mike -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
