You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that setting the cache limit via [[PINDiskCache sharedCache] setByteLimit:_] doesn't affect the disk cache in [[PINRemoteImageManager sharedImageManager] defaultImageCache] but it seems like that should be the case right?
The text was updated successfully, but these errors were encountered:
Wow. I've been using PINRemoteImage in a project for over a year (still in beta) and have been absolutely baffled by the ever-increasing storage usage even when I am judiciously calling trim on the sharedCache. byteCount on the sharedCache always comes back as 0 and I never could figure out why, since it's storing over a gigabyte of items on my phone. This issue by @lappp9 finally explained it to me, there's a special cache for remote images that is the one taking up all the space.
So +1 on this. I wonder how many people are just using PINRemoteImage, not realizing that they can't trim the disk cache down because it's being stored using a different mechanism than they'd expect?
It seems that setting the cache limit via
[[PINDiskCache sharedCache] setByteLimit:_]
doesn't affect the disk cache in[[PINRemoteImageManager sharedImageManager] defaultImageCache]
but it seems like that should be the case right?The text was updated successfully, but these errors were encountered: