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. ,
    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

Solutions on the web

via Stack Overflow by Kiran
, 1 year ago
Failed to allocate a 69050892 byte allocation with 628840 free bytes and 614KB 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 mozilla.com by Unknown author, 1 year ago
Failed to allocate a 526092 byte allocation with 12655240 free bytes and 109MB until OOM
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 aakashshah94
, 7 months ago
Failed to allocate a 1000012 byte allocation with 557840 free bytes and 544KB until OOM
java.lang.OutOfMemoryError: Failed to allocate a 69050892 byte allocation with 628840 free bytes and 614KB until OOM	at dalvik.system.VMRuntime.newNonMovableArray(Native Method)