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 mozilla.com by Unknown author, 1 year ago
Failed to allocate a 16396 byte allocation with 14928836 free bytes and 106MB until OOM
via GitHub by iceberg1369
, 1 year ago
Failed to allocate a 67108876 byte allocation with 4194208 free bytes and 16MB until OOM
via Stack Overflow by Paweł O
, 1 year ago
Failed to allocate a 156828 byte allocation with 40472 free bytes and 39KB until OOM
via GitHub by matthiasprieth
, 10 months ago
Failed to allocate a 105678412 byte allocation with 16777216 free bytes and 65MB until OOM
via GitHub by langyazhouwl
, 1 year ago
Failed to allocate a 138240019 byte allocation with 7739952 free bytes and 84MB until OOM
via Stack Overflow by Kiran
, 1 year ago
Failed to allocate a 69050892 byte allocation with 628840 free bytes and 614KB until OOM
java.lang.OutOfMemoryError: Failed to allocate a 16396 byte allocation with 14928836 free bytes and 106MB until OOM	at dalvik.system.VMRuntime.newNonMovableArray(Native Method)