Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Try adding these lines to your manifest: "android:hardwareAccelerated="false"" and "android:largeHeap="true"" as it seems to work for some cases. See also this article about handling bitmaps on android's documentation: https://goo.gl/8LVrzp

  2. ,

    The memory is leaking. Try to analyze the HEAP or use LeakCanacy (https://github.com/square/leakcanary) to figure out where is the exact problem.

Solutions on the web

via Stack Overflow by Sir George
, 1 year ago
Failed to allocate a 144764940 byte allocation with 16777120 free bytes and 27MB until OOM
via Stack Overflow by Nick Dettore
, 2 years ago
Failed to allocate a 144000012 byte allocation with 1048576 free bytes and 63MB until OOM
via Stack Overflow by ywj7931
, 1 year ago
Failed to allocate a 52428812 byte allocation with 33553680 free bytes and 48MB until OOM
via Stack Overflow by Vinothini
, 6 months ago
Failed to allocate a 39306252 byte allocation with 16777216 free bytes and 27MB until OOM
via Stack Overflow by ashu_legacy
, 1 year ago
Failed to allocate a 132710412 byte allocation with 4194208 free bytes and 46MB until OOM
java.lang.OutOfMemoryError: Failed to allocate a 144764940 byte allocation with 16777120 free bytes and 27MB until OOM	at dalvik.system.VMRuntime.newNonMovableArray(Native Method)	at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)	at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:609)