Message-ID: <gh-pgjdbc-pgjdbc-3089-c1887218145@github.com>
From: "bokken (@bokken)" <noreply+bokken@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 11 Jan 2024 13:59:25 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3089: Metaspace Memory leak: Thread.inheritedAccessControlContext
In-Reply-To: <gh-pgjdbc-pgjdbc-3089@github.com>
References: <gh-pgjdbc-pgjdbc-3089@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: bokken
X-GitHub-Comment-Id: 1887218145
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3089
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3089#issuecomment-1887218145
Content-Type: text/plain; charset=utf-8

If there is a leak, the heap dump should show the connection objects with
references to the problematic class loader. Perhaps there are other details
on the connection objects which could provide a hint of where they are
leaked from.

On Thu, Jan 11, 2024 at 7:23 AM Dave Cramer ***@***.***>
wrote:

> queue seems to be empty on all instances I checked
>
> If the queue is empty the thread should terminate, and it should no longer
> hold the resources.
>
> I think you are right about an application leak. Something is holding a
> reference to the connections so gc() is not collecting them and they aren't
> in the queue.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pgjdbc/pgjdbc/issues/3089#issuecomment-1887155340>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAW3U3OGL52XVVRVOGJCCYLYN7RVLAVCNFSM6AAAAABBTEMBACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXGE2TKMZUGA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>