-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8255848: -Xlog:gc+heap+exit shows "used 0K" #1051
Conversation
👋 Welcome back sjohanss! A progress list of the required criteria for merging this PR into |
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.
lgtm.
@kstefanj 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 27 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 |
/integrate |
@kstefanj Since your change was applied there have been 44 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 397972e. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this small change to improve the exit heap-log for G1.
Currently if all allocations fit into one region the exit log will faulty state that the usage is 0K:
This is cause by G1 using
used_unlocked()
, which doesn't take the current allocation region(s) into account. My proposed change is to check if theHeap_lock
is taken and if so useused()
instead ofused_unlocked()
. For the exit logging the lock will be held, but this log is printed usingG1CollectedHeap::print_on()
and we might want to allow calling this without requiring holding the heap lock.Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1051/head:pull/1051
$ git checkout pull/1051