On Thu, Apr 7, 2011 at 5:16 AM, NURAIZ yousuf_...@yahoo.com wrote:
Why our native heap size is increased every time we run the application?
Based on the detailed information you provided, I can conclude with
confidence that it's because you're using more memory every time you run the
John,
I've seen something similar causing memory leaks, preventing GC from
working, although not in Android:
public class Item {
static HashtablegHash = new Hashtable();
private String key;
public Item(String key) {
this.key = key;
gHash.put(key, this);
}
public void finalize() {
On Mon, Oct 18, 2010 at 4:58 PM, John Gaby jg...@gabysoft.com wrote:
I appear to have a memory leak(s) in my application, and I am trying
to get a handle on it by trying to understand more about garbage
collection. I have created the following application.
Here I have a class 'MyClass', and
There must be something else going on in your app. All standard apps
rely on onDestroy() being called and certainly do not do all you
mentioned in your message.
Be very careful with what you do with the Context. An Activity is a
Context and you might be leaking it without knowing it. What you are
4 matches
Mail list logo
