Skip to content
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

8280414: Memory leak in DefaultProxySelector #821

Closed

Conversation

MBaesken
Copy link
Member

@MBaesken MBaesken commented Feb 11, 2022


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/821/head:pull/821
$ git checkout pull/821

Update a local copy of the PR:
$ git checkout pull/821
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/821/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 821

View PR using the GUI difftool:
$ git pr show -t 821

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/821.diff

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 11, 2022

👋 Welcome back mbaesken! 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 openjdk bot changed the title Backport fe77250fa450ec803d2818dc90c5bf156521d537 8280414: Memory leak in DefaultProxySelector Feb 11, 2022
@openjdk
Copy link

openjdk bot commented Feb 11, 2022

This backport pull request has now been updated with issue from the original commit.

@openjdk
Copy link

openjdk bot commented Feb 11, 2022

@MBaesken This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8280414: Memory leak in DefaultProxySelector

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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 ready Pull request is ready to be integrated rfr Pull request is ready for review labels Feb 11, 2022
@mlbridge
Copy link

mlbridge bot commented Feb 11, 2022

Webrevs

@MBaesken
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Feb 15, 2022

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

  • fd7d0d3: 8280526: x86_32 Math.sqrt performance regression with -XX:UseSSE={0,1}
  • bd420d2: 8279076: C2: Bad AD file when matching SqrtF with UseSSE=0
  • 29eb422: 8281520: JFR: A wrong parameter is passed to the constructor of LeakKlassWriter

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Feb 15, 2022

@MBaesken Pushed as commit fe17b44.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport clean integrated Pull request has been integrated
1 participant