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
8254668: JVMTI process frames on thread without started processing #627
8254668: JVMTI process frames on thread without started processing #627
Conversation
👋 Welcome back stefank! 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.
Looks good. Thanks for fixing this.
@stefank 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 6 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ 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 Stefan,
thanks for fixing.
With this change the assertion in pr #119 does not fail anymore.
The fix looks good to me but I'm not an ZGC expert, neither a Reviewer :)
/integrate |
@stefank Since your change was applied there have been 19 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit db9dcdf. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I hit the following assert in some tests runs that I've been doing:
The stack traces for this has been:
The code inspects the top frame of a suspended java thread. However, there's nothing in the code that starts the watermark processing of the thread, so the code asserts when sender calls on_iteration.
We only have to call start_processing/on_iteration when oops are being read. The failing code does not inspect any oops, so I turn of the on_iteration call by settings process_frame to false.
To notify the readers of the code that vframeFor doesn't process the oops, I've renamed the function to vframeForNoProcess to give a visual cue.
I found this bug when running this command line:
makec ../build/fastdebug/ test TEST=test/hotspot/jtreg/vmTestbase/nsk/jvmti JTREG="JAVA_OPTIONS=-XX:+UseZGC -Xmx2g -XX:ZCollectionInterval=1 -XX:ZFragmentationLimit=0.01" JTREG_EXTRA_PROBLEM_LISTS=ProblemList-zgc.txt
Five tests consistently asserts with this command line. All tests pass with the proposed fix.
Recommendations of tests to run are welcome. I intend to get this run through tier1-3, but haven't yet.
Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/627/head:pull/627
$ git checkout pull/627