-
Notifications
You must be signed in to change notification settings - Fork 223
8283469: Don't use memset to initialize members in FileMapInfo and fix memory leak #397
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 zgu! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
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.
Backport lgtm. Please add empty line before integrating.
@@ -195,6 +193,13 @@ FileMapInfo::~FileMapInfo() { | |||
assert(_dynamic_archive_info == this, "must be singleton"); // not thread safe | |||
_dynamic_archive_info = NULL; | |||
} |
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.
Original change adds an empty line here. Please insert.
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.
Fixed. Thanks for the review, @TheRealMDoerr
@zhengyu123 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 4 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 |
/integrate |
Going to push as commit 0355888.
Your commit was automatically rebased without conflicts. |
@zhengyu123 Pushed as commit 0355888. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I would like to backport this patch to 17u, to fix a memory leak, also eliminates dangerous memset call, could potentially result in fatal crash.
The original patch does not apply cleanly, due to JDK-8261455, where it changed FileMapInfo's constructor signature to pass in full_path as a parameter. The conflict is resolved manually by initializing _full_path to nullptr.
I also bought down following code from JDK-8261455, given it is a P4 enhancement, I don't see it is a candidate for backport itself. But following code obviously fixes a bug that leaves file open after use.
Test:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/397/head:pull/397
$ git checkout pull/397
Update a local copy of the PR:
$ git checkout pull/397
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/397/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 397
View PR using the GUI difftool:
$ git pr show -t 397
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/397.diff