Message-ID: <gh-pgjdbc-pgjdbc-3089-c1883278751@github.com>
From: "embuc (@embuc)" <noreply+embuc@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 09 Jan 2024 15:35:32 +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: embuc
X-GitHub-Comment-Id: 1883278751
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-1883278751
Content-Type: text/plain; charset=utf-8

Oh, such a blast from the past, haven't used that for more than a decade - lo and behold -it's still there and I had to try it. It does confirm that: '...classes from previous runs are still loaded in memory, thus causing a memory leak (use a profiler to confirm)...' Which corresponds with my findings (it simply states which contexts contain leaks).