Databases
StackOverflow2013
Postsdbo
POAndroid - recover from low memory condition
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid - recover from low memory condition
    primarykey
    data
    text
    <p>I'm developing an application with very intense image processing where I have multiple <code>ListFragments</code> in the horizontal <code>FragmentStatePagerAdapter</code>. I aggressively employ practically every trick and suggestion I was able to find here and elsewhere. I download bitmaps and save these to SD and as soft reference memory cache. </p> <p>Nevertheless as I use the app at certain point I start seeing messages in LogCat just like one below</p> <pre><code>11-05 15:57:43.951: I/dalvikvm-heap(5449): Clamp target GC heap from 32.655MB to 32.000MB 11-05 15:57:43.951: D/dalvikvm(5449): GC_FOR_MALLOC freed 0K, 24% free 11512K/14983K, external 17446K/17896K, paused 64ms 11-05 15:57:44.041: D/dalvikvm(5449): GC_EXTERNAL_ALLOC freed &lt;1K, 24% free 11511K/14983K, external 17258K/17896K, paused 77ms </code></pre> <p>If I continue, messages above will become more urgent</p> <pre><code>11-05 16:02:09.590: D/dalvikvm(5449): GC_FOR_MALLOC freed 0K, 23% free 11872K/15239K, external 17497K/17896K, paused 71ms 11-05 16:02:09.700: D/dalvikvm(5449): GC_EXTERNAL_ALLOC freed &lt;1K, 23% free 11872K/15239K, external 17497K/17896K, paused 84ms 11-05 16:02:09.720: E/dalvikvm-heap(5449): 192816-byte external allocation too large for this process. 11-05 16:02:09.800: I/dalvikvm-heap(5449): Clamp target GC heap from 33.057MB to 32.000MB 11-05 16:02:09.800: D/dalvikvm(5449): GC_FOR_MALLOC freed 0K, 23% free 11872K/15239K, external 17497K/17896K, paused 68ms 11-05 16:02:09.800: E/GraphicsJNI(5449): VM won't let us allocate 192816 bytes </code></pre> <p>And inevitably the app will crash with OutOfMemoryException The symptoms are classical memory leak. Yet in my <code>Fragment#onDestroy</code> method I cancel all the pending tasks, unbind and nullify the views and call Bitmap#recycle. Interestingly enough, I do see GC calls in the LogCat but even if I pause for extended period the memory is never reclaimed.</p> <p>My gut feeling is that it is continuous re-reading of images from SD that causes degradation and inevitable demise</p> <p>Here's utility cleaning method I'm using trying to shake off drawables (there's more as I said to cancel pending/running tasks and empty ListView adapters)</p> <pre><code>public static void unbindDrawables(View view, final boolean agressive) { if (view instanceof ViewGroup) { for (int i = 0; i &lt; ((ViewGroup) view).getChildCount(); i++) { unbindDrawables(((ViewGroup) view).getChildAt(i), agressive); } if (!AdapterView.class.isInstance(view)) { ((ViewGroup) view).removeAllViews(); } } else { Drawable bmp = view.getBackground(); if (bmp == null &amp;&amp; ImageView.class.isInstance(view)) bmp = ((ImageView) view).getDrawable(); if (bmp != null) { bmp.setCallback(null); if (agressive &amp;&amp; (TaggedDrawable.class.isInstance(bmp))) { Bitmap bm = ((BitmapDrawable) bmp).getBitmap(); if (bm != null) { if (DEBUG) Log.i(TAG, "Forcing bitmap recycle for " + bmp); bm.recycle(); bm = null; view.destroyDrawingCache(); view = null; } } } } } </code></pre> <p>Needless to say I'm seriously disturbed at this point and will greatly appreciate any suggestions </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBostone
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid - recover from low memory condition
      1. USBostone
      1. VTBountyStart
    2. VO
      singulars
      1. POAndroid - recover from low memory condition
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid - recover from low memory condition
      1. USDharmendra
      1. VTFavorite
    1. COTake a heap dump using DDMS or the `Debug` class, bring it up in MAT in Eclipse, and see what's going on with your heap. This works best for bitmap-related issues if you run your app on Honeycomb (or, presumably, Ice Cream Sandwich, though I haven't tried that yet). Bitmap memory was largely invisible to MAT pre-Honeycomb, but in Honeycomb they started allocating bitmap memory on the standard (non-native) heap, so you should get better results for figuring out who is holding onto what.
      singulars
      1. POAndroid - recover from low memory condition
      1. USCommonsWare
    2. COUnfortunately the app is v7+ using v4 compatibility lib. I was also trying to use System.gc() and got into some weird issues like infinite loop where one GC call triggers another one and so on. I also learned that catching OutOfMemoryError is useless at the very best
      singulars
      1. POAndroid - recover from low memory condition
      1. USBostone
    3. CO"Unfortunately the app is v7+ using v4 compatibility lib" -- so? **Run** your app on Honeycomb or Ice Cream Sandwich for the purposes of tracking down your memory issues. Whatever you fix there will also help you on older Android devices. The leaks aren't changing between versions, but MAT's ability to help you does.
      singulars
      1. POAndroid - recover from low memory condition
      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