Baseflow
memory requirements
We found that the memory increases significantly when there are a large number of instantaneous requests. Can the upper layer process the maximum number of requests through the queue when loading images, and remove the excess from the queue? cached_network_image will depend on flutter_cache_manager, and the queue of flutter_cache_manager cannot actually solve the instantaneous large number of requests. At present, our processing is: before using cached_network_image, through queue management (it will monitor whether the image is loaded), set the maximum number of simultaneous requests, and reject the most advanced request when it exceeds. After this processing, the memory performance is significantly reduced. I wonder if the developers of cached_network_image can handle this requirement?
have the same issue. my app has a hundreds images which are loaded in parallel. approx after 1 or two minutes app is crashing. the issue is stable reproduced on a number of devices. if I just changed CachedNetworkImage to Image.network, everything works fine.
Hi, @playtikasmirnov why are you thinking CachedNetworkImage is the problem ? I load a lot of images as well, and i am trying to understand why my memory consuming is so high. But CachedNetworkImage is just a way to download images from storage instead of network ? is image size is good, there is no difference i guess
