Apologies, that description is pretty lousy. A more explicit description of
the leak (the one in my test in https://github.com/openjdk/jdk/pull/26296)
would be: A class loaded by classloader 'C' statically references an
Executor created via newSingleThreadExecutor(threadFactory). The
ThreadFactory
On 11/07/2025 15:42, Chris Dennis wrote:
Hi All,
I believe I've identified a bug in
Executors.AutoShutdownDelegatedExecutorService that can trigger a
classloader leak even in the presence of "correct" Executor
lifecycling. AutoShutdownDelegatedExecutorService only unlinks the
PhantomReferenc
x.
Cheers,
√
Viktor Klang
Software Architect, Java Platform Group
Oracle
From: core-libs-dev on behalf of Chris Dennis
Sent: Friday, 11 July 2025 16:42
To: core-libs-dev
Subject: ClassLoader Leak via Executors.newSingleThreadExecutor(...)
Hi All,
I believe I've i
Hi All,
I believe I've identified a bug in
Executors.AutoShutdownDelegatedExecutorService that can trigger a
classloader leak even in the presence of "correct" Executor lifecycling.
AutoShutdownDelegatedExecutorService only unlinks the PhantomReference used
for cleanup handling when it is shutdown
