It’s standard practice to cache images when displaying, as an image viewed once is likely to be viewed again, and then it’s good to save on the data and latency by loading it from disk (or even memory).
However, it’s also standard practice to have an upper size boundary on this cache and to implement an eviction mechanism for the cache once it has reached its capacity.
This is probably a case of misconfiguration or something overlooked during implementation.
Apps have to download the thumbnails and whatever you actually click on.
Though that is a shitload.
Get SDMaid. Even the free version makes cleanup a lot easier.
It’s standard practice to cache images when displaying, as an image viewed once is likely to be viewed again, and then it’s good to save on the data and latency by loading it from disk (or even memory).
However, it’s also standard practice to have an upper size boundary on this cache and to implement an eviction mechanism for the cache once it has reached its capacity.
This is probably a case of misconfiguration or something overlooked during implementation.
I think the app needs to have a regular cash wipe build in, it causes Crashes for me.
Yeah, mine freezes on open sometimes which I suspect is the cache.
It should have an upper limit with the oldest access time items being evicted first.
It should be capped at 750mb it doesn’t need more and it wouldn’t be a problem if it just deletes the oldest stuff when its not needed anymore.
Yeah, that’s what I mean. But it needs to be done by access time, not oldest item, as you don’t want frequently used things to be evicted.
@kuro_neko@lemmy.ca
True, didn’t think about that, but yeah shure, your own PFP, banner and some community icons should probably stay in.
SDMaid actually open source (GPLv3) now!
The dev rebuilt the app for modern Android and made it open source
https://github.com/d4rken-org/sdmaid-se