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 T-BONE
, 1 year ago
Failed to allocate a 2560012 byte allocation with 1668568 free bytes and 1629KB until OOM
via Stack Overflow by Rohit_Ramkumar
, 2 years ago
Failed to allocate a 1508952 byte allocation with 56504 free bytes and 55KB until OOM
via Stack Overflow by GINCHER
, 2 years ago
Failed to allocate a 86252412 byte allocation with 1048576 free bytes and 63MB until OOM
via Stack Overflow by Earthling
, 2 years ago
Failed to allocate a 5035548 byte allocation with 5011320 free bytes and 4MB until OOM
java.lang.OutOfMemoryError: Failed to allocate a 2560012 byte allocation with 1668568 free bytes and 1629KB until OOM at dalvik.system.VMRuntime.newNonMovableArray(Native Method) at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method) at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:609) at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:444) at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:1080) at android.content.res.Resources.loadDrawableForCookie(Resources.java:2635) at android.content.res.Resources.loadDrawable(Resources.java:2540)