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

Thank you for the report. It would help if you could provide a reproducer or a heapdump.

`LazyCleaner` thread should terminate after (30000ms of inactivity, `pgjdbc.config.cleanup.thread.ttl` system property), so it should not generate a long-lasting leak.

Do you think you redeploy multiple times within 30sec window?

As you are using Java 17, we could probably make a patch that uses Java's `Cleaner` for Java 9+, so it is more robust.