8284532: Memory leak in BitSet::BitMapFragmentTable in JFR leak profiler

[zhengyu123]

A clean and low risk backport to fix a memory leak.

---

Progress

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

Issue

• JDK-8284532: Memory leak in BitSet::BitMapFragmentTable in JFR leak profiler

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 369

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

Using diff file

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

[bridgekeeper]

👋 Welcome back zgu! 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]

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

[openjdk]

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

8284532: Memory leak in BitSet::BitMapFragmentTable in JFR leak profiler

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 1 new commit pushed to the master branch:

• 90d4233: 8284622: Update versions of some Github Actions used in JDK workflow

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

[mlbridge]

Webrevs

• 00: Full (e7988126)

[zhengyu123]

/integrate

[openjdk]

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

• 70d3583: 8282170: JVMTI SetBreakpoint metaspace allocation test
• 0955aca: 8285394: Compiler blackholes can be eliminated due to stale ciMethod::intrinsic_id()
• db26df6: 8284549: JFR: FieldTable leaks FieldInfoTable member
• a1da138: 8284620: CodeBuffer may leak _overflow_arena
• c1e1719: 8274735: javax.imageio.IIOException: Unsupported Image Type while processing a valid JPEG image
• bb7b764: 8279529: ProblemList java/nio/channels/DatagramChannel/ManySourcesAndTargets.java on macosx-aarch64
• 40c7bf2: 8282293: Domain value for system property jdk.https.negotiate.cbt should be case-insensitive
• d67ca11: 8279842: HTTPS Channel Binding support for Java GSS/Kerberos
• ae9b334: 8280684: JfrRecorderService failes with guarantee(num_written > 0) when no space left on device.
• b751b3c: 8285445: cannot open file "NUL:"
• ... and 8 more: https://git.openjdk.java.net/jdk17u-dev/compare/2a799c8e1880ebb93fc348b2a74cc31c4c5195f5...master

Your commit was automatically rebased without conflicts.

[openjdk]

@zhengyu123 Pushed as commit cf2b20f.

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