-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OOM in scheduleNextRender #600
Comments
Thanks for the report, I'll check that. |
Those stacktraces originates from framework code. Nothing has changed here between versions 1.2.12 an 1.2.15. Not sure what I can do without steps to reproduce. I guess that some changes in your project caused memory starvation and it is just revealed here as OOME. I'll close this issue due to no known action which can be performed by me. However, it can be reopened if there is some new info. |
Actually I do think that the issue is somewhere with your library. I switched back and forth between the two versions since 1.2.15 was released and those errors do not appear with 1.2.12 but reappear as soon as I switch to 1.2.15. |
OK, I'll to reproduce that. |
On which Android version did those issues occur? |
It looks like it is only occurring on 6, 7 and 8. |
OK, I was able to reproduce it on stress tests. It seems that some filedescriptor is closed more than one time. I'll investigate and fix it asap. |
Great news, thank you very much! |
Sorry for the delay. I'll try to reproduce that. |
After updating from
1.2.12
to1.2.15
I see a lot of OutOfMemoryErrors in GifDrawable.scheduleNextRender. I only see this in firebase over a wide range of Android versions and devices, i could not recreate the issue locally.In a background thread I am just loading a
GifDrawable
from aRandomAccessFile.getFD()
that I am closing after creating theGifDrawble
. On the main thread I am passing theGifDrawable
to aImageView
and callingcurrentFrameIndex
andnumberOfFrames
, as well aspause(), start(), stop()
andseekTo(0)
once or twice.The text was updated successfully, but these errors were encountered: