On Jul 29, 12:15 pm, choff <[email protected]> wrote: > [...] This would > suggest that ANDROID itself is not letting go of the Activity > instances. That some how they are being queued up or hung on to...
Again, your best bet is to look for the objects in the hprof data and see what's holding on to them. There are a large number of applications that don't have this problem, so you're not bumping up against a fundamental platform flaw. You should probably read this blog post about how to avoid some common leaks: http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
