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.