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 leak during cleanup #81

Open
bubblesupreme opened this issue Mar 23, 2023 · 0 comments
Open

Memory leak during cleanup #81

bubblesupreme opened this issue Mar 23, 2023 · 0 comments

Comments

@bubblesupreme
Copy link

bubblesupreme commented Mar 23, 2023 •
edited
Loading

There is a problem here. Buckets and list cleanup must be synchronized. Otherwise, if we concurrently call Set we may end up with an empty list and non-empty buckets. In this case we got memory leak like this. There is a small leak, but it's still there. At the next cleanup, these objects will be removed, but new leaking objects will appear again.
karlseguin added a commit that referenced this issue Apr 14, 2023
@karlseguin
Attempt to make Clear concurrency-safe
a25552a 
This is an attempt at fixing #81 without imposing a performance hit on the
cache's "normal" (get/set/fetch) activity. Calling "Clear" is now considerably
more expensive.
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
@bubblesupreme