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 Maksim Dmitriev
, 1 year ago
Failed to allocate a 233280012 byte allocation with 10567360 free bytes and 176MB until OOM
via GitHub by peterneubauer
, 2 years ago
Failed to allocate a 10077708 byte allocation with 4463250 free bytes and 4MB until OOM
via GitHub by locomain
, 2 years ago
Failed to allocate a 24385548 byte allocation with 1477232 free bytes and 1442KB until OOM
via GitHub by yigepang
, 9 months ago
Failed to allocate a 3126652 byte allocation with 905352 free bytes and 884KB until OOM
Empty query.