-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8286870: Memory leak with RepeatCompilation #8744
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
Conversation
|
👋 Welcome back thartmann! A progress list of the required criteria for merging this PR into |
|
@TobiHartmann The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
vnkozlov
left a comment
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.
Good.
|
@TobiHartmann 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 23 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 |
|
You got github testing failures. |
|
Thanks for the review, Vladimir. The github failures seem unrelated and due to missing Loom support on 32-bit: |
chhagedorn
left a comment
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.
Looks good!
|
Thanks, Christian! |
|
/integrate |
|
Going to push as commit 69ff86a.
Your commit was automatically rebased without conflicts. |
|
@TobiHartmann Pushed as commit 69ff86a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
While using
RepeatCompilationin combination with replay compilation and stress options to reproduce an intermittent issue, I noticed that it does not free the compiler thread arena after each compilation, leading to a (temporary) memory leak and out of memory errors. For example, each compilation of JDK-8280696 allocates an additional 1218 kB.The fix is to simply add a
ResourceMarkin the loop.Thanks,
Tobias
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8744/head:pull/8744$ git checkout pull/8744Update a local copy of the PR:
$ git checkout pull/8744$ git pull https://git.openjdk.java.net/jdk pull/8744/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8744View PR using the GUI difftool:
$ git pr show -t 8744Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8744.diff