-
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
java.lang.NullPointerException #3629
Comments
it looks like that this commit 53438b9?w=1 . fix this NPM crash. is it? @Judds |
then I can only reback to 4.7.1 to fix the problem now? |
That looks plausible. You could also use the latest snapshot: http://bumptech.github.io/glide/dev/snapshots.html |
This issue has been automatically marked as stale because it has not had activity in the last seven days. It will be closed if no further activity occurs within the next seven days. Thank you for your contributions. |
We are facing the same issue while we are using glide Version 4.9. Please confirm which version has fixed this issue. Because 4.9 seems to be the latest one. @sjudd |
I have the same issue in my project:
|
Got same issue while using below libs: api 'com.github.bumptech.glide:glide:4.9.0' Fatal Exception: java.lang.NullPointerException: Null reference used for synchronization (monitor-enter) |
I have the same issue in my project when I update to 4.9 |
I'm facing the same issue, is there some news? com.bumptech.glide.load.engine.EngineResource.release + 107 (EngineResource.java:107)
--
| com.bumptech.glide.load.engine.Engine.release + 286 (Engine.java:286)
| com.bumptech.glide.request.SingleRequest.releaseResource + 340 (SingleRequest.java:340)
| com.bumptech.glide.request.SingleRequest.clear + 330 (SingleRequest.java:330)
| com.bumptech.glide.manager.RequestTracker.clearRemoveAndMaybeRecycle + 79 (RequestTracker.java:79)
| com.bumptech.glide.manager.RequestTracker.clearRemoveAndRecycle + 66 (RequestTracker.java:66) Glide Version:4.9.0 |
This is the highest firing crash in our app, it would seem prudent to do a patch release to fix it. |
Why this issue status is closed, did anyone tried below version? where it seems looking fixed: |
Any news? I have the same issue on my app from crashlytics: |
4.9.0:
Integration libraries:
Device/Android Version:
Issue details / Repro steps / Use case background:
Stack trace / LogCat:
The text was updated successfully, but these errors were encountered: