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.

Sign up for GitHub

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

Jump to bottom

Memory Peak during removeExpiredObjects #102

Open
Janscho opened this issue Aug 4, 2017 · 0 comments
Open

Memory Peak during removeExpiredObjects #102

Janscho opened this issue Aug 4, 2017 · 0 comments

Comments

@Janscho
Copy link

Janscho commented Aug 4, 2017 •
edited
Loading

Memory can peak very high in removeExpiredObjects (which might lead to crashes), caused by the for-loop which accesses all elements inside the cache. This could be easily fixed by wrapping the code after the for-loop inside an autoreleasepool.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Janscho