title: Android memory leak with static final
body: <p>The question is on using static final constants which apparently causes memory leaks: I have been searching for information on how not to cause memory leaks in Android Apps. One big problem is using private static final for constants. Apparently that is how constants should be defined. But static final means it hangs around after a rotation and means the Activity cannot be cleared.</p>
  
  <p>Obviously I am misunderstanding something. I know that putting variables in the Application context allows them to hang around without causing problems.</p>
  
  <p>As a general question on memory leaks: There are lots of information on memory leaks, but I cannot find anything that sums up all the information clearly. Any recommendations where it is all fully explained. </p>