pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3886: fix: avoid memory leaks in Java <= 21 caused by Thread.inheritedAccessControlContext
Date: Thu, 04 Dec 2025 12:08:41 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> > What happens if ForkJoinPool.commonPool() is unavailable (custom security manager)?
>
> Frankly, I do not think it is a real scenario.
>
> > No handling for RejectedExecutionException from execute()
>
> Frankly, `commonPool()` should not reject unless it shuts down. I think we should not add workarounds for RejectedExecutionException.
Fair enough. After giving this more thought I really do think we should consider leaving the code as is and providing a multi-release jar that targets java 9+. I would imagine most folks that are running into the memory leak issue are using Java 9 or greater
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #3886: fix: avoid memory leaks in Java <= 21 caused by Thread.inheritedAccessControlContext
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox