-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8354872: Clarify java.lang.Process resource cleanup #25884
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
Recommend closing streams when no longer in use. Describe the implementation closing streams when no longer referenced. Clarify the interactions between inputStream and inputReader and errorStream and errorReader. Add advice and example using try-with-resources to open and close streams.
👋 Welcome back rriggs! A progress list of the required criteria for merging this PR into |
@RogerRiggs 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 199 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. ➡️ To integrate this PR with the above commit message to the |
@RogerRiggs 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. |
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.
The addendum on resource management looks very useful, thanks! 💯
Shall we also
- Create a dedicated section on resource management
- Document the effect of
destroy()
anddestroyForcibly()
(andonExit()
?) on releasing resources
…to the ProcessBuilder constructor. Plus copyright update
The copyright years on these files will need an update. |
Please also review the CSR. |
* @apiNote | ||
* Use {@link #getInputStream()} and {@link #inputReader()} with extreme care. | ||
* The {@code BufferedReader} may have buffered input from the input stream. | ||
* Use either this method or an {@linkplain #inputReader(Charset) input reader} |
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.
I think this should be {@linkplain #inputReader() input reader}
(i.e. the one that doesn't take a CharSet) to match what was there previously before the changes in this PR.
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.
Conundrum... The readable text refers to "an input reader" and covers the case of either inputReader method.
But including both links makes the sentence hard to read, so I picked the more expressive reader method to link to.
Reverting to no-arg version.
Ditto below.
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.
But including both links makes the sentence hard to read, so I picked the more expressive reader method to link to.
It didn't realize you had intentionally used the CharSet
one. If you think the CharSet would provide better guidance to the developers, then I think it's OK to switch to that one.
The updated changes look good to me. I just noticed a few typoes which I've reviewed inline. I'll review the CSR now. |
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.
Thank you Roger for these updates. This looks good to me.
/integrate |
Going to push as commit afb4a1b.
Your commit was automatically rebased without conflicts. |
@RogerRiggs Pushed as commit afb4a1b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport :jdk25 |
@RogerRiggs the backport was successfully created on the branch backport-RogerRiggs-afb4a1be-jdk25 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk25, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:
|
Improve the documentation of Process use of system resources.
Describe the implementation closing streams when no longer referenced.
Clarify the interactions between inputStream and inputReader and errorStream and errorReader.
Add advice and example using try-with-resources to open and close streams.
Recommend closing streams when no longer in use.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25884/head:pull/25884
$ git checkout pull/25884
Update a local copy of the PR:
$ git checkout pull/25884
$ git pull https://git.openjdk.org/jdk.git pull/25884/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25884
View PR using the GUI difftool:
$ git pr show -t 25884
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25884.diff
Using Webrev
Link to Webrev Comment