On Dec 17, 7:45 am, "B++" <bet...@gmail.com> wrote: > The problem is that this happens even if no objects are instantiated > using the loaded class. There seems a problem with garbage collector, > which doesn't seem to release resources about the loaded class on > Destroy even if there are no references to it.
It usually turns out that something is holding a reference to whatever it is that isn't getting thrown away. The best way to figure this out is to get the HPROF output and run it through jhat or MAT. See also: http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/heap-profiling.html;hb=HEAD http://kohlerm.blogspot.com/ -- 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
