Hi rukiman, The best way to determine what is wrong in your scenario is taking some heap dumps and analysing them with MAT, for example.
Markus Kohler's blog have a good tutorial to do this: http://kohlerm.blogspot.com/2009/04/analyzing-memory-usage-off-your-android.html This "Activity Leak" is common when some reference to Context remains on memory after the Activity destruction. Look for some static reference to it (its just a guess) Regards, Felipe Silveira On Thu, Sep 24, 2009 at 3:40 AM, rukiman <ruksh...@optushome.com.au> wrote: > > In my app activity A creates activity B, however when the back key is > pressed it goes back to activity A. This is a simplified version of my > application. > > I would expect memory to be reclaimed when going back to Activity A. > Going to activity B allocates more memory. > > I am using dumpsys meminfo to get the allocated kbs. > > How can I easily tell what memory is creeping? I do not keep any > references to activity B. > > I know about the ddms allocation tracker, but wondering if there is a > more better tool to figure this out. > > I read somewhere about someone during a heap dump. How do I do that? > > > -- Felipe Silveira Engenharia da Computação Universidade Federal de Itajubá http://www.felipesilveira.com.br MSN: felipeuni...@hotmail.com Skype: fsunifei ------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
