-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8316658: serviceability/jvmti/RedefineClasses/RedefineLeakThrowable.java fails intermittently #15882
Conversation
…ava fails intermittently increase Metaspace size and loop count to avoid OOME in nominal case
👋 Welcome back jpbempel! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
This seems okay if it helps the test run reliably. I don't know a better way to test the absence of a memory leak. If this fails again, maybe we need to rewrite RedefineClassHelper to only generate the class bytes once, not each time.
This is a trivial change and seems to already have David's implicit approval in the CR, so I don't think you need to wait 24 hours. You can if you want though.
@jpbempel 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 49 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@coleenp, @dholmes-ora) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks! |
Hold on! I tested a change to 17M only. Sure 24M will work fine to avoid the OOM, but does it still fail without the original fix? The boost to 1000 iterations is untested and may lead to new failures, so I will have to re-test this again before it is integrated. |
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.
The test still fails with these new settings. As per JBS I found 17m worked fine with the existing iterations and still caused an unfixed VM to fail. With 24M and 500 iterations the unfixed VM passes.
/reviewers 2 |
@dholmes-ora |
On my side, 17M with 500 iterations on an unpatched VM does not fail. |
Re-testing at 17M/700 |
Okay 17M/700 seems to work okay in our CI, and fails without the fix. |
Thanks! |
/sponsor |
Going to push as commit 84390dd.
Your commit was automatically rebased without conflicts. |
@dholmes-ora @jpbempel Pushed as commit 84390dd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
increase Metaspace size and loop count to avoid OOME in nominal case
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15882/head:pull/15882
$ git checkout pull/15882
Update a local copy of the PR:
$ git checkout pull/15882
$ git pull https://git.openjdk.org/jdk.git pull/15882/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15882
View PR using the GUI difftool:
$ git pr show -t 15882
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15882.diff
Webrev
Link to Webrev Comment