-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native crash playing Gifs #219
Comments
Fixed for 3.4, moving to 3.5 to find the real cause. |
Our app in production also has the same issue. we uses glide:3.5.2 + okhttp-integration:1.2.2 combo. |
Ok so after some discussion, this happens because the framework doesn't expect us to reconfigure Bitmaps until after it has finished drawing them. The only way to guarantee that we do so is to delay calling reconfigure by posting to a Handler before returning the Bitmaps to the pool. This is what the warning at the bottom of the javadoc for Since we're doing this for GIFs, this particular issue should be fixed. We don't do this generally, so it's still possible this could randomly crop up when loading other types of images. We should look in to posting all returns, not just those for GIFs. |
Hi, Thanks a lot. |
If this is still affecting people, I don't have any great ideas. If you can provide a sample app and a new stack trace I can look in to it more. |
I have this same error when working with GIFs |
@kiaanpillay without a consistent repro we can't do much: #219 (comment) |
I got same error on Android 4.4 Galaxy Core2 (kanas)
|
We seem to have a problem drawing Bitmaps that are either recycled or being modified concurrently. As far as I can tell this crash was introduced here: 32f7a82.
For 3.4 I'll stick with reverting that change. However, I don't believe the change itself is incorrect, so there's likely something wrong in GifDrawable. I'll target the subsequent fix for 3.5 and/or a dot release.
The text was updated successfully, but these errors were encountered: