-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[Android] Too many images caused Fresco's TooManyBitmapsException #6649
Comments
@phones24 did you find a solution? |
Same issue here |
@ms88privat, I optimized my app so it's not cached too many images. I also added some more JPEG compression and scale the images down a bit. I also wrote a path that adds error information to the event. Still would be nice to have some control over fresco caching and logging from android app |
@phones24 you wrote "I optimized my app so it's not cached too many images". How did you do that? Is it possible to control the tag in how it will use any caches? |
@itinance, I just cut the amount of prerendered scenes with big images. No magic here, unfortunately. |
Hi there! This issue is being closed because it has been inactive for a while. But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/android-too-many-images-caused-frescos-toomanybitmapsexception- Product Pains has been very useful in highlighting the top bugs and feature requests: Also, if this issue is a bug, please consider sending a pull request with a fix. |
My application is showing many images on many scenes (prerendered with Navigator).
From time to time, after couple of reloading almost all images got disappeared.
I've added some logging to Fresco module and discovered
onFailure: failure: com.facebook.imagepipeline.common.TooManyBitmapsException
for every image I'm trying to show.
Also I'm noticed that Fresco caches is basically not configured. It uses default configuration for ImagePipelineConfig.
I there a way to configure Fresco image pipeline for my app?
Also onLoadEnd for Image component provides no info on what's happened. Would be nice to have nativeEvent telling the cause of failure.
The text was updated successfully, but these errors were encountered: