Skip to content

8362123: ClassLoader Leak via Executors.newSingleThreadExecutor(...)#26296

Closed
chrisdennis wants to merge 1 commit intoopenjdk:masterfrom
chrisdennis:JDK-8362123
Closed

8362123: ClassLoader Leak via Executors.newSingleThreadExecutor(...)#26296
chrisdennis wants to merge 1 commit intoopenjdk:masterfrom
chrisdennis:JDK-8362123

Conversation

@chrisdennis
Copy link
Contributor

@chrisdennis chrisdennis commented Jul 14, 2025

Executors shutdown via shutdownNow() should have their cleanables cleaned to prevent a classloader leak. This can happen if a classloader exists that both references the wrapped executor and is referenced by the delegate executor.

To quote @Martin-Buchholz:

BTW: I find Cleaners much harder to use than old finalize, and it looks like I'm not the only one!


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

  • JDK-8362123: ClassLoader Leak via Executors.newSingleThreadExecutor(...) (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26296

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Jul 14, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Jul 14, 2025

Hi @chrisdennis, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user chrisdennis" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Jul 14, 2025

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

8362123: ClassLoader Leak via Executors.newSingleThreadExecutor(...)

Reviewed-by: vklang, alanb

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 169 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@viktorklang-ora, @AlanBateman) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Jul 14, 2025

@chrisdennis 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.

@openjdk openjdk bot added the core-libs core-libs-dev@openjdk.org label Jul 14, 2025
@chrisdennis
Copy link
Contributor Author

chrisdennis commented Jul 14, 2025

/covered

Covered under my employment by IBM. I've set the author email on my commits to my IBM address, and I can be reached there for validation reasons if necessary. My Github user is also a member of the IBM Github organization.

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Jul 14, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Jul 14, 2025

Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@chrisdennis
Copy link
Contributor Author

@robilad : Apologies for the direct invoke, but I've seen you facilitate this process before, so hope this is still the right way to bump things:

I've waited a "few business days" but have seen no movement on the OCA verification, and have noticed no verification email inbound to me (chris.w.dennis@ibm.com).

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 18, 2025

@chrisdennis This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@chrisdennis
Copy link
Contributor Author

/keepalive - awaiting action from IBM to get OCA paperwork processed.

@openjdk
Copy link

openjdk bot commented Sep 8, 2025

@chrisdennis The pull request is being re-evaluated and the inactivity timeout has been reset.

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Sep 26, 2025
@openjdk openjdk bot added the rfr Pull request is ready for review label Sep 26, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 26, 2025

Webrevs

@viktorklang-ora
Copy link
Contributor

@chrisdennis Looks like your OCA approval was resolved, so I'll have a look at your Pull-Request now.

Comment on lines +129 to +138
ClassLoader classLoader = Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());

ReferenceQueue<?> queue = new ReferenceQueue<>();
Reference<?> reference = new PhantomReference(classLoader, queue);

classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
classLoader = null;

assertTrue(ForceGC.wait(() -> queue.poll() != null));
Reference.reachabilityFence(reference);
Copy link
Contributor

Choose a reason for hiding this comment

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

reachabilityFence should be placed in a finally-block as per: https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/lang/ref/Reference.html#reachabilityFence(java.lang.Object)

Suggested change
ClassLoader classLoader = Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());
ReferenceQueue<?> queue = new ReferenceQueue<>();
Reference<?> reference = new PhantomReference(classLoader, queue);
classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
classLoader = null;
assertTrue(ForceGC.wait(() -> queue.poll() != null));
Reference.reachabilityFence(reference);
try {
ClassLoader classLoader = Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());
ReferenceQueue<?> queue = new ReferenceQueue<>();
Reference<?> reference = new PhantomReference(classLoader, queue);
classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
classLoader = null;
assertTrue(ForceGC.wait(() -> queue.poll() != null));
} finally {
Reference.reachabilityFence(reference);
}

ReferenceQueue<?> queue = new ReferenceQueue<>();
Reference<?> reference = new PhantomReference(classLoader, queue);

classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we split up and assert that the defining loader of IsolatedClass is "classLoader"? It's important to be confident of that when looking at this test.

ReferenceQueue<?> queue = new ReferenceQueue<>();
Reference<?> reference = new PhantomReference(classLoader, queue);

classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
Copy link
Contributor

Choose a reason for hiding this comment

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

Something like this:

Suggested change
classLoader.loadClass("AutoShutdown$IsolatedClass").getDeclaredMethod("shutdown", Consumer.class).invoke(null, shutdown);
classLoader.loadClass("AutoShutdown$IsolatedClass")
.getDeclaredMethod("shutdown", Consumer.class)
.invoke(null, shutdown);


public static class IsolatedClass {

private static final ExecutorService executor = Executors.newSingleThreadExecutor(new IsolatedThreadFactory());
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
private static final ExecutorService executor = Executors.newSingleThreadExecutor(new IsolatedThreadFactory());
private static final ExecutorService executor =
Executors.newSingleThreadExecutor(new IsolatedThreadFactory());

@ParameterizedTest
@MethodSource("shutdownMethods")
void testShutdownUnlinksCleaner(Consumer<ExecutorService> shutdown) throws Exception {
ClassLoader classLoader = Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
ClassLoader classLoader = Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());
ClassLoader classLoader =
Utils.getTestClassPathURLClassLoader(ClassLoader.getPlatformClassLoader());

}

private static Stream<Arguments> shutdownMethods() {
return Stream.<Consumer<ExecutorService>>of(e -> e.shutdown(), e -> e.shutdownNow()).map(Arguments::of);
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
return Stream.<Consumer<ExecutorService>>of(e -> e.shutdown(), e -> e.shutdownNow()).map(Arguments::of);
return Stream.<Consumer<ExecutorService>>of(
e -> e.shutdown(),
e -> e.shutdownNow()
).map(Arguments::of);

Executors shutdown via `shutdownNow()` should have their cleanables cleaned to
prevent a classloader leak. This can happen if a classloader exists that both
references the wrapped executor and is referenced by the delegate executor.
@chrisdennis
Copy link
Contributor Author

@viktorklang-ora @AlanBateman I believe I've covered all the requested changes.

@openjdk
Copy link

openjdk bot commented Sep 26, 2025

@chrisdennis Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@chrisdennis
Copy link
Contributor Author

Apologies for the force push, force of habit from my normal work.

Copy link
Contributor

@viktorklang-ora viktorklang-ora left a comment

Choose a reason for hiding this comment

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

Looks good, thanks for addressing this!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 2, 2025
@chrisdennis
Copy link
Contributor Author

Apologies gentlemen, but do I need to do something to move this on? If I understand correctly it's just a /integrate command to the Skara machinery now, but I don't believe I have the permissions to trigger that?

@AlanBateman
Copy link
Contributor

Yes, you need to use "/integrate", and then one of us will sponsor.

@chrisdennis
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Oct 9, 2025
@openjdk
Copy link

openjdk bot commented Oct 9, 2025

@chrisdennis
Your change (at version eaec0b5) is now ready to be sponsored by a Committer.

@AlanBateman
Copy link
Contributor

/sponsor

@openjdk
Copy link

openjdk bot commented Oct 10, 2025

Going to push as commit d5a2079.
Since your change was applied there have been 185 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 Oct 10, 2025
@openjdk openjdk bot closed this Oct 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Oct 10, 2025
@openjdk
Copy link

openjdk bot commented Oct 10, 2025

@AlanBateman @chrisdennis Pushed as commit d5a2079.

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

@chrisdennis
Copy link
Contributor Author

/backport jdk25u

@openjdk
Copy link

openjdk bot commented Oct 12, 2025

@chrisdennis To use the /backport command, you need to be in the OpenJDK census and your GitHub account needs to be linked with your OpenJDK username (how to associate your GitHub account with your OpenJDK username).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants