Skip to content

Conversation

RogerRiggs
Copy link
Contributor

@RogerRiggs RogerRiggs commented Jun 18, 2025

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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8356311 to be approved

Issues

  • JDK-8354872: Clarify java.lang.Process resource cleanup (Bug - P4)
  • JDK-8356311: Clarify java.lang.Process resource cleanup (CSR)

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

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.
@bridgekeeper
Copy link

bridgekeeper bot commented Jun 18, 2025

👋 Welcome back rriggs! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jun 18, 2025

@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:

8354872: Clarify java.lang.Process resource cleanup

Reviewed-by: jpai

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 master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added csr Pull request needs approved CSR before integration rfr Pull request is ready for review labels Jun 18, 2025
@openjdk
Copy link

openjdk bot commented Jun 18, 2025

@RogerRiggs The following label will be automatically applied to this pull request:

  • core-libs

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.

@mlbridge
Copy link

mlbridge bot commented Jun 18, 2025

Webrevs

Copy link
Contributor

@vy vy left a 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

  1. Create a dedicated section on resource management
  2. Document the effect of destroy() and destroyForcibly() (and onExit()?) on releasing resources

…to the ProcessBuilder constructor.

Plus copyright update
@jaikiran
Copy link
Member

The copyright years on these files will need an update.

@RogerRiggs
Copy link
Contributor Author

Please also review the CSR.
JDK-8356311: Clarify java.lang.Process resource use

* @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}
Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Member

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.

@jaikiran
Copy link
Member

jaikiran commented Jul 2, 2025

The updated changes look good to me. I just noticed a few typoes which I've reviewed inline. I'll review the CSR now.

Copy link
Member

@jaikiran jaikiran left a 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.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed csr Pull request needs approved CSR before integration labels Jul 3, 2025
@RogerRiggs
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Jul 7, 2025

Going to push as commit afb4a1b.
Since your change was applied there have been 221 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 7, 2025
@openjdk openjdk bot closed this Jul 7, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jul 7, 2025
@openjdk
Copy link

openjdk bot commented Jul 7, 2025

@RogerRiggs Pushed as commit afb4a1b.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@RogerRiggs
Copy link
Contributor Author

/backport :jdk25

@openjdk
Copy link

openjdk bot commented Jul 7, 2025

@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:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit afb4a1be from the openjdk/jdk repository.

The commit being backported was authored by Roger Riggs on 7 Jul 2025 and was reviewed by Jaikiran Pai.

Thanks!

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:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-RogerRiggs-afb4a1be-jdk25:backport-RogerRiggs-afb4a1be-jdk25
$ git checkout backport-RogerRiggs-afb4a1be-jdk25
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-RogerRiggs-afb4a1be-jdk25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants