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 Image if Large -> Error: Pool hard cap violation? #11326

Closed
kosiakMD opened this issue Dec 6, 2016 · 3 comments
Closed

Android Image if Large -> Error: Pool hard cap violation? #11326

kosiakMD opened this issue Dec 6, 2016 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@kosiakMD
Copy link

kosiakMD commented Dec 6, 2016

Get Image remotely and want to show in full screen
iOS - OK! Android - some loading and showing, some just black screen (modal default background), some 'red' Errors, caused if failed Native Image.getSize

When show small - OK.

Not enough memory! Small - OK. Problem persists only when very large Images: Full HD - only not showing, but without Error, larger cause the error written previously

Error: Pool hard cap violation? Hard cap = 75497472 Used size = 60880784 Free size = 0 Request size = 20072448
@kosiakMD
Copy link
Author

kosiakMD commented Dec 9, 2016

It's real memory leak, and may be related with Fresco

@caozhifeng
Copy link

caozhifeng commented Dec 30, 2016

I hava the same problem. Android - when showing a image in full screen is ok, but not shown in a modal

@hramos
Copy link
Contributor

hramos commented Jul 20, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos added the Icebox label Jul 20, 2017
@hramos hramos closed this as completed Jul 20, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Jul 20, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 20, 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

5 participants