com.bumptech.glide.load.engine.CallbackException

lib:4.15.1

com.bumptech.glide.load.engine.CallbackException: Unexpected exception thrown by non-Glide code at com.bumptech.glide.load.engine.EngineJob.callCallbackOnLoadFailed(EngineJob.java:175) at com.bumptech.glide.load.engine.EngineJob$CallLoadFailed.run(EngineJob.java:402) at android.os.Handler.handleCallback(Handler.java:751) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6682) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410) Caused by: java.lang.OutOfMemoryError: Failed to allocate a 2430012 byte allocation with 1615504 free bytes and 1577KB until OOM at dalvik.system.VMRuntime.newNonMovableArray(Native Method) at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method) at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:700) a$

Start with the stack trace locations in EngineJob.java, especially lines 175 and 402, and inspect how the callback failure relates to Android BitmapFactory.decodeStream. The report provides no reproduction, requested behavior, or test; a useful next step is to establish a reproducible case and determine whether Glide or calling code owns the out-of-memory failure before defining done.

Written by the indexing model from the issue text.