Skip to content
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

Closed
phones24 opened this issue Mar 25, 2016 · 6 comments
Closed

[Android] Too many images caused Fresco's TooManyBitmapsException #6649

phones24 opened this issue Mar 25, 2016 · 6 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@phones24
Copy link

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.

@phones24 phones24 changed the title [Android] Too many images cause Fresco's TooManyBitmapsException [Android] Too many images caused Fresco's TooManyBitmapsException Mar 25, 2016
@ms88privat
Copy link

@phones24 did you find a solution?

@itinance
Copy link
Contributor

Same issue here

@phones24
Copy link
Author

@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

@itinance
Copy link
Contributor

@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?

@phones24
Copy link
Author

@itinance, I just cut the amount of prerendered scenes with big images. No magic here, unfortunately.

@mkonicek
Copy link
Contributor

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:
https://productpains.com/product/react-native?tab=top

Also, if this issue is a bug, please consider sending a pull request with a fix.

@facebook facebook locked as resolved and limited conversation to collaborators Jul 19, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

7 participants