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 aakashshah94
, 9 months ago
Failed to allocate a 1000012 byte allocation with 557840 free bytes and 544KB until OOM
via Stack Overflow by Ricky Patel
, 9 months ago
Failed to allocate a 244588824 byte allocation with 11397108 free bytes and 79MB until OOM
via Stack Overflow by Yonatan Alkobi
, 7 months ago
Failed to allocate a 1016486028 byte allocation with 22393786 free bytes and 479MB until OOM
Empty query.