Vincent Tsao's Library tagged "memory leak" → View Popular, Search in Google

Aug

2011

Fastersite: Finding memory leaks

gent.ilcore.com/...finding-memory-leaks.html

- Preview

memory leak memory

Apr

2010

Avoiding Memory Leaks | Android Developers

developer.android.com/...avoiding-memory-leaks.html

- Preview

android memory leak tech

As part of my job, I ran into memory leaks issues in Android applications and they are most of the time due to the same mistake: keeping a long-lived reference to a Context.
There are two easy ways to avoid context-related memory leaks. The most obvious one is to avoid escaping the context outside of its own scope. The example above showed the case of a static reference but inner classes and their implicit reference to the outer class can be equally dangerous. The second solution is to use the Application context. This context will live as long as your application is alive and does not depend on the activities life cycle. If you plan on keeping long-lived objects that need a context, remember the application object. You can obtain it easily by calling Context.getApplicationContext() or Activity.getApplication().
1 more annotation(s)...
- In summary, to avoid context-related memory leaks, remember the following:
  
  Do not keep long-lived references to a context-activity (a reference to an activity should have the same life cycle as the activity itself)
  Try using the context-application instead of a context-activity
  Avoid non-static inner classes in an activity if you don't control their life cycle, use a static inner class and make a weak reference to the activity inside. The solution to this issue is to use a static inner class with a WeakReference to the outer class, as done in ViewRoot and its W inner class for instance
  A garbage collector is not an insurance against memory leaks