-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8352942: jdk/jfr/startupargs/TestMemoryOptions.java fails with 32-bit build #24646
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 tkiriyama! A progress list of the required criteria for merging this PR into |
@tkiriyama 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 58 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 (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@tkiriyama 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. |
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 fine to me.
/integrate |
@tkiriyama |
/sponsor Trivial. |
Going to push as commit c3de94c.
Your commit was automatically rebased without conflicts. |
@phohensee @tkiriyama Pushed as commit c3de94c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi All,
I would like to add this bug fix for the bug in jdk/jfr/startupargs/TestMemoryOptions.java.
I was unable to reproduce the reported problem in java versions 11 and later. Therefore, I made a pull request for 8u before.
openjdk/jdk8u-dev#641
However, the latest java should be fixed, as the bugs described below will potentially remain in the test.
This test contains 24 test cases and fails the "ThreadBufferSizeExceedMemorySize" case.
The cause of this bug is the memory allocation issue, which occurs only on 32-bit Server VM, not on Client VM or 64-bit JDK. The failure happens because Server VM's default heap size reduces available memory space, causing JFR to fail memory allocation.
To resolve this issue, -Xmx256M is explicitly set, matching the Client VM default heap size, ensuring sufficient memory space remains available for JFR.
I believe that this test verifies that the combination of memory options for JFR is valid or invalid and that the MaxHeapSize setting does not affect the verification.
Change has been verified locally, test-fix only, no risk.
Would someone please review this fix?
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24646/head:pull/24646
$ git checkout pull/24646
Update a local copy of the PR:
$ git checkout pull/24646
$ git pull https://git.openjdk.org/jdk.git pull/24646/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24646
View PR using the GUI difftool:
$ git pr show -t 24646
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24646.diff
Using Webrev
Link to Webrev Comment