Databases
StackOverflow2013
Postsdbo
POdialog box memory leak or stubborn GC?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdialog box memory leak or stubborn GC?
    primarykey
    data
    text
    <p>When I load up my app, It takes around 3Mb of RAM. I have an <code>ImageButton</code> on my first activity which calls the function <code>showRecords</code>, which displays a dialog box.</p> <p>Once the dialog box is opened, it can be closed by clicking outside of the box (which will call the <code>dismiss()</code> method). The problem I am having is that after the dialog box has been closed, the amount of RAM used by my application does not return to its previous state (it can remain over a Mb more If I include another stuff in the dialog - but the example retains around 2-300kb)</p> <pre><code> public void showRecords(View v){ Dialog recordDialog = new Dialog(this); recordDialog.requestWindowFeature(Window.FEATURE_NO_TITLE); recordDialog.setCanceledOnTouchOutside(true); recordDialog.setContentView(R.layout.record); recordDialog.show(); } </code></pre> <p>The record.xml file has an image background, and another ImageView with a picture.</p> <p>I have tried using MAT, and can see no Dialog objects in memory. I also have been using DDMS to perform garbage collections, but the RAM value never returns to what I would expect.</p> <p>Is something binding to the activity? or is the GC just refusing the reclaim the memory?</p> <p>As this is my first activity, it remains alive throughout and doesn't seem to close if I need more heap space (for some reason). Therefore I'm quite interested in reclaiming a Mb of memory when it is not needed.</p> <p>EDIT - record.xml</p> <pre><code>&lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="wrap_content" android:layout_height="wrap_content" android:background="@drawable/background" android:orientation="vertical" &gt; &lt;ImageView android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/recordspage" android:layout_marginTop="5dp" android:layout_gravity="center_horizontal" android:layout_marginLeft="10dp" android:layout_marginRight="10dp" /&gt; &lt;/LinearLayout&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJordyNewc
    1. USJordyNewc
    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. POdialog box memory leak or stubborn GC?
      1. USplackemacher
      1. VTFavorite
    2. VO
      singulars
      1. POdialog box memory leak or stubborn GC?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is in `R.layout.record`? "doesn't seem to close if I need more heap space (for some reason)" -- that's normal behavior, activities do not automatically close due to low heap space (despite hints in the documentation to the contrary).
      singulars
      1. POdialog box memory leak or stubborn GC?
      1. USCommonsWare
    2. COAh, I didn't realize that was normal behaviour. Thanks for clearing that up. I will add record.xml to my question. I seem to lose some memory even without setting the contentView though.
      singulars
      1. POdialog box memory leak or stubborn GC?
      1. USJordyNewc
    3. COWell, some of the memory will be `@drawable/recordspage` and `@drawable/background`, as drawable resources are held onto even if they are not being referenced presently, IIRC. "Is something binding to the activity?" -- if you BACK-button out of the activity, it should no longer show up in MAT. You might also use MAT to sort by biggest memory culprits, and examine it before and after launching the dialog.
      singulars
      1. POdialog box memory leak or stubborn GC?
      1. USCommonsWare
 

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