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

    This was issue #159 in Fresco, and was fixed recently, in v1.3.0.

  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 GitHub by 1049884729
, 6 months ago
Fatal Exception thrown on Scheduler.Worker thread.
via GitHub by hudan2714
, 8 months ago
Fatal Exception thrown on Scheduler.Worker thread.
via GitHub by TheTomTom3901
, 10 months ago
Fatal Exception thrown on Scheduler.Worker thread.
via GitHub by android-cui
, 6 months ago
Fatal Exception thrown on Scheduler.Worker thread.
via GitHub by mycold
, 10 months ago
Fatal Exception thrown on Scheduler.Worker thread.
via GitHub by princeHago
, 3 weeks ago
Fatal Exception thrown on Scheduler.Worker thread.
java.lang.OutOfMemoryError: Failed to allocate a 8355852 byte allocation with 2497147 free bytes and 2MB until OOM	at dalvik.system.VMRuntime.newNonMovableArray(Native Method)	at android.graphics.Bitmap.nativeCreate(Native Method)	at android.graphics.Bitmap.createBitmap(Bitmap.java:812)	at android.graphics.Bitmap.createBitmap(Bitmap.java:789)	at android.graphics.Bitmap.createBitmap(Bitmap.java:756)