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 GitHub by AlstonLin
, 1 year ago
Failed to allocate a 14909452 byte allocation with 7555208 free bytes and 7MB until OOM
via mozilla.com by Unknown author, 1 year ago
Failed to allocate a 43628 byte allocation with 35676 free bytes and 34KB until OOM
via GitHub by aakashshah94
, 8 months ago
Failed to allocate a 1000012 byte allocation with 557840 free bytes and 544KB until OOM
via Stack Overflow by user2217535
, 2 years ago
Failed to allocate a 2097164 byte allocation with 338434 free bytes and 330KB until OOM
via Stack Overflow by Ricky Patel
, 8 months ago
Failed to allocate a 244588824 byte allocation with 11397108 free bytes and 79MB until OOM
java.lang.OutOfMemoryError: Failed to allocate a 14909452 byte allocation with 7555208 free bytes and 7MB until OOM	at dalvik.system.VMRuntime.newNonMovableArray(VMRuntime.java)