Databases
StackOverflow2013
Postsdbo
POWhy does Android leak memory due to static Drawable if it's callback is reset?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
    primarykey
    data
    text
    <p>I was just following this article on how to avoid memory leaks : <a href="http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html">android developer blog</a> Following is the code snippet used :</p> <pre><code>private static Drawable sBackground; @Override protected void onCreate(Bundle state) { super.onCreate(state); TextView label = new TextView(this); label.setText("Leaks are bad"); if (sBackground == null) { sBackground = getDrawable(R.drawable.large_bitmap); } label.setBackgroundDrawable(sBackground); setContentView(label); } </code></pre> <p>It is said that the drawable has a callback reference to textview (and indirectly to the activity); which will be preserved on rotation - and hence memory leak. </p> <p><strong>My query</strong> is that won't the drawable's callback be reset on rotation - it would get hold of the new textview (which will hold the new context).. hence allowing the previous instances of textview/context to be GC'ed.</p> <p><strong>EDIT</strong> : The answers I get are on how to "solve" the issue - I am not looking for that ! Please re-read the query. I am adding more details. When activity is launched, the references are :</p> <blockquote> <p>Drawable1 -> TextView1 -> Activity1</p> </blockquote> <p>When rotated, Activity1 and TextView1 are destroyed but not Drawable1</p> <blockquote> <p>Drawable1 -> TextView2 -> Activity2</p> </blockquote> <p>This means, <strong>Activity1 and TextView1 are free to be GC'ed</strong> - as no other object is having a reference to them. So what is leaking ?</p> <p>Am I wrong in this understanding ? Or is it that the Drawable can have multiple views as callbacks ? (Looking at the source code, I dont see a list of callbacks on Drawable). </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJaguar
    1. USJaguar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. USJaguar
      1. VTFavorite
    1. COIf you don't change your layout on rotation it is a good thing to consider handling rotation differently: without activity re-creation (it is possible). So this will solve your trouble. Another thing with memory leaks, is that anyway it is worth to remove background drawable in `onDestroy`.
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. USAlexey A.
    2. COThanks, but I am concerned with why the leak is happening in the first case. I understand how to solve the problem.
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. USJaguar
    3. COOn rotation activity is "re-created", so your previous view/image are connected with previous Activiy context - so you have a memory leak. if you clean up in onDestroy() it will solve the issue
      singulars
      1. POWhy does Android leak memory due to static Drawable if it's callback is reset?
      1. USAlexey A.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload