Curious your thoughts on memory usage vs RN's <Image />

Hey so my app loads a lot of images remotely, and allows users to take photos and upload them. I see a fair number of memory related issues in my app as a result. Particularly my API doesn’t thumbnail any images so remote images load in as large images and from what I can tell from RN’s <Image /> is that it’s not giving me a ton of support in downsampling. Thus lots of crashes.

I’m curious your evaluation on what RN’s <Image /> is doing on iOS and Android to help with local and remote image in regards to memory / disk consumption. And how this differs from react-native-fast-image (and the underlying Glide / SDWebImage)

Any insight would be very helpful, thank you!

[kevinresol]

I can confirm the memory issue. I have a FlatList with FastImage, at any time there will be 9 - 12 images visible (a 3 column by 3 row layout). The memory usage (as seen in xcode) shoots up to 600MB and the app crashes. This happens when I scroll the list down to around the 100th image.

As a reference, when using standard RN Image, the memory usage is ~90MB max even scrolling pass the 100th image.

[bitshadow]

@pavanmehta91 I have just written https://medium.com/@bitshadow/finding-memory-leaks-react-native-app-ios-46e6eeb50c8c . Hope this is helpful.