Message-ID: <gh-pgjdbc-pgjdbc-3089-c1887121529@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 11 Jan 2024 13:02:55 +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: davecramer
X-GitHub-Comment-Id: 1887121529
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-1887121529
Content-Type: text/plain; charset=utf-8

> > you could try building the jar using #3090 but if gc() isn't running I fail to see how using Cleaner will work
> 
> @davecramer I built the snapshot with #3090 and tried but I get same thing :/ GC is definitely running but I can see that it frees up about ~15MB of Metaspace but thats not enough (when close the limit) and the OOM is thrown. @vlsi the queue seems to be empty on all instances I checked.

What this tells us is that the issue is not with our code as this uses java 9+ Cleaner.