-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
TooManyBitmapsException cause no display AGAIN #1351
Comments
@narychen Truth is that You are negligent. Look the follow code.
*Decrease the mCount and mSize By mUnpooledBitmapsCounter.getReleaser(), returned as a CloseableReference . * |
@huangjunkun Maybe you were right.
And the output is |
@narychen |
I found that quit the app and launch again will lead to bitmapCounter start counting on the number of what you last quit and never decrease down below that number. I think there may be some problem with the special region of Android memory where decompressed image stored on On Android 4.x and lower.
|
Duplicating to #1980 |
This problem has been issued many times, but I don't think it has been solved.
I added a comment at the bottom of this issue #213
The image will not show after a long time running if you have a lot of pictures to render because of TooManyBitmapsException.
But imagePipeline.clearCaches() or shutDown() doesn't solve it.
I checked the code in com.facebook.imagepipeline.memory.BitmapCounter and didn't find any code clear the mCount and mSize to zero when you call clearCaches().
So I think there may be something missed here.
The text was updated successfully, but these errors were encountered: