Skip to content

JDK-8303071: Memory leaks in libjdwp #12716

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

Closed
wants to merge 2 commits into from
Closed

Conversation

jcking
Copy link
Contributor

@jcking jcking commented Feb 22, 2023

Fix minor memory leaks in libjdwp.


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

Issue

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12716/head:pull/12716
$ git checkout pull/12716

Update a local copy of the PR:
$ git checkout pull/12716
$ git pull https://git.openjdk.org/jdk pull/12716/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 12716

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12716.diff

Signed-off-by: Justin King <jcking@google.com>
@bridgekeeper
Copy link

bridgekeeper bot commented Feb 22, 2023

👋 Welcome back jcking! 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 added the rfr Pull request is ready for review label Feb 22, 2023
@openjdk
Copy link

openjdk bot commented Feb 22, 2023

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

  • serviceability

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.

@openjdk openjdk bot added the serviceability serviceability-dev@openjdk.org label Feb 22, 2023
@mlbridge
Copy link

mlbridge bot commented Feb 22, 2023

Webrevs

Signed-off-by: Justin King <jcking@google.com>
Copy link
Contributor

@sspitsyn sspitsyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good.
Thank you for taking care about it.
Thanks,
Serguei

@openjdk
Copy link

openjdk bot commented Feb 23, 2023

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

8303071: Memory leaks in libjdwp

Reviewed-by: sspitsyn

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 36 new commits pushed to the master branch:

  • fcaf871: 8302028: Port fdlibm atan2 to Java
  • 07e976a: 8303081: Serial: Remove unused VM_MarkSweep
  • 8de841d: 8302667: Improve message format when failing to load symbols or libraries
  • f893d23: 8303024: (fs) WindowsFileSystem.supportedFileAttributeViews can use Set.of
  • d7ada66: 8303084: G1 Heap region liveness verification has inverted return value
  • 5d7e7e2: 8302760: Improve liveness/remembered set verification for G1
  • b0e0f37: 8303067: G1: Remove unimplemented G1FullGCScope::heap_transition
  • 1a62a12: 8302880: Fix includes in g1ConcurrentMarkObjArrayProcessor files
  • ee37af4: 8302975: Remove redundant mark verification during G1 Full GC
  • 83bea26: 8300575: JVMTI support when using alternative virtual thread implementation
  • ... and 26 more: https://git.openjdk.org/jdk/compare/10b4cc9eb49c14a6be03b3f53e97037529169ed1...master

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 the ready Pull request is ready to be integrated label Feb 23, 2023
@jcking
Copy link
Contributor Author

jcking commented Feb 23, 2023

Tests look unrelated and seem to be failing in other PRs.

@jcking
Copy link
Contributor Author

jcking commented Feb 23, 2023

/integrate

@openjdk
Copy link

openjdk bot commented Feb 23, 2023

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

  • f113b04: 8302927: Unproblemlist Fuzz.java from ProblemList-zgc.txt again
  • 1bab93b: 8303073: (bf) Temporarily reinstate private DirectByteBuffer(long, int) constructor
  • 221f346: 8303047: avoid NULL after 8301661
  • 23e9d9d: 8302811: NMT.random_reallocs_vm fails if NMT is off
  • fcaf871: 8302028: Port fdlibm atan2 to Java
  • 07e976a: 8303081: Serial: Remove unused VM_MarkSweep
  • 8de841d: 8302667: Improve message format when failing to load symbols or libraries
  • f893d23: 8303024: (fs) WindowsFileSystem.supportedFileAttributeViews can use Set.of
  • d7ada66: 8303084: G1 Heap region liveness verification has inverted return value
  • 5d7e7e2: 8302760: Improve liveness/remembered set verification for G1
  • ... and 30 more: https://git.openjdk.org/jdk/compare/10b4cc9eb49c14a6be03b3f53e97037529169ed1...master

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Feb 23, 2023

@jcking Pushed as commit 2cf8b86.

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

@jcking jcking deleted the libjdwp-leak branch February 23, 2023 15:24
@dholmes-ora
Copy link
Member

Just a sanity check here. That memory was allocated using *callback->alloc not jvmtiAllocate - is it correct to release with jvmtiDeallocate?

@jcking
Copy link
Contributor Author

jcking commented Feb 23, 2023

callback->alloc is jvmtiAllocate and callback->free is jvmtiDeallocate. It is setup in transport.c, which is also the one which frees. So it is fine in this case.

@dholmes-ora
Copy link
Member

Thanks! Now I can join the dots there.

Copy link
Contributor

@plummercj plummercj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

@jcking In the future please wait for a second review before pushing any hotspot related changes unless the reviewer agrees that the changes are trivial. thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

4 participants