Checking the heap dump is perfectly, just make sure you're not doing it with the debugger attached. Also make sure to force a GC a couple of times on your process before taking a heap dump.
On Thu, Jun 30, 2011 at 12:19 AM, Atlan <[email protected]> wrote: > That's what I learn in this conversation. > > But as said before I made a heap dump because my app crashed after changing > the > orientation in the emulator for about 6 to 10 times. This caused me to > check the heap and because I found no problem in my code I started to make > heap dumps. > The dumps showed my Activity 6 to 10 times in memory so it was clear to me > that something is referencing back to the Activity. > Specially because you explain in your posts that Drawables link back to the > Activity with a callback-function and that this could cause memory leaks > like I head. > > Anyway - thanks for your help. > > -- > 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 -- Romain Guy Android framework engineer [email protected] -- 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
