-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8267752: KVHashtable doesn't deallocate entries #4501
Conversation
👋 Welcome back coleenp! A progress list of the required criteria for merging this PR into |
@coleenp This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 25 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Coleen,
seems to be right.
I did a little test (filling a KV<int, int> hashtable with 500mio entries and releasing it) and was confused when RSS did not go down es expected; but this seems to be a glibc issue (repeating the test did not allocate twice as much memory, so the second round of mallocs reused the first frees).
(Update: this is entirely an glibc issue of not releasing memory to the OS)
See my question inline about unlink(). Otherwise this is fine. This was only ever used in CDS dumping, right?
Cheers, Thomas
Thanks Ioi and Thomas for the code reviews. |
Going to push as commit 72b3b0a.
Your commit was automatically rebased without conflicts. |
Add a free_entry iteration to the destructor of ~KVHashtables.
Tested with tier1-3.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4501/head:pull/4501
$ git checkout pull/4501
Update a local copy of the PR:
$ git checkout pull/4501
$ git pull https://git.openjdk.java.net/jdk pull/4501/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4501
View PR using the GUI difftool:
$ git pr show -t 4501
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4501.diff