I don't have any advice, I'm just very interested in hearing if and how you make an progress diagnosing, debugging and fixing this sort of issue. I'm still trying to fix what looks like memory leak in my app. All I have succeeded in doing is reducing the total memory used, thereby making the bug dramatically less noticeable.
Thanks, -Matt Kanninen On Dec 16, 8:19 am, freezy <[email protected]> wrote: > Hi all, > > I'm trying to locate a memory leak in my app (it's client for a > mediacenter). So I start it up, go to the screen that lists all movies, go > back to my home activity, trigger the GC a few times manually via DDMS, dump > the memory heap, pull it, convert it and load it into MIT in Eclipse. > > Now the movie list screen is pretty heavy, around 800k of movie objects, > which should be freed when I go back to the home screen. However, it stays > allocated, with the GC root as a local variable in the main thread at > ActivityThread.ContextCleanupInfo > (see attached screenshot). > > I've tried searching but there is no documentation on this class, not even > in the source code. Is there any way to avoid this kind of behavior? Am I > doing something wrong or is the problem in Android? My app is open source > and can be checked out here[1]. > > Any hints and suggestions appreciated! > > [1]http://code.google.com/p/android-xbmcremote/ > > leak-contextcleanupinfo.png > 120KViewDownload -- 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
