Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different Default Caches #155

Open
lappp9 opened this issue Dec 22, 2016 · 1 comment
Open

Different Default Caches #155

lappp9 opened this issue Dec 22, 2016 · 1 comment
Assignees
Milestone

Comments

@lappp9
Copy link

lappp9 commented Dec 22, 2016

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?

@garrettmoon garrettmoon added this to the 3.0 milestone Jan 20, 2017
@garrettmoon garrettmoon self-assigned this Jan 20, 2017
@flyosity
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants