Reset memory categories on successful DestroyJavaVM - #17668
Merged
Conversation
pshipton
reviewed
Jun 26, 2023
pshipton
reviewed
Jun 26, 2023
Reset the runtime-filled memory category information if DestroyJavaVM succeeds. Fixes: eclipse-openj9#17267 Signed-off-by: Graham Chapman <graham_chapman@ca.ibm.com>
Contributor
Author
|
@pshipton I guess you may as well review/test. |
Member
|
jenkins test sanity,sanity.openjdk win jdk11 |
Contributor
Author
|
There's a bunch of failures, but I can't imagine they're related to this change, which only has an impact on repeated create/destroy of the VM. |
Member
|
Failures unrelated to this change. |
pshipton
approved these changes
Jun 27, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reset the runtime-filled memory category information if DestroyJavaVM succeeds.
Fixes: #17267