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

2025-07-22 Thread Jaikiran Pai
Hello Chris, In the past the OCA verification has sometimes taken more than a week or two, so please wait a few more days for the verification to be completed. -Jaikiran On 23/07/25 4:30 am, Chris Dennis wrote: Is there a process I can (or should?) be following to get my PR for fixing this t

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

2025-07-22 Thread Chris Dennis
Is there a process I can (or should?) be following to get my PR for fixing this through OCA verification, or do I just need to be a little more patient? Thanks, Chris On Tue, 15 Jul 2025 at 07:59, Chris Dennis wrote: > Apologies, that description is pretty lousy. A more explicit description >

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

2025-07-15 Thread Chris Dennis
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

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

2025-07-15 Thread Alan Bateman
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

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

2025-07-14 Thread Viktor Klang
Hi Chris, I've opened the following JBS issue based on your email: https://bugs.openjdk.org/browse/JDK-8362123 If you intend to open a PR against the issue, please make sure that the OCA status is in order and that there's a regression test associated with the proposed fix. Cheers, √ Viktor