Re: BUG #16707: Memory leak

Jaime Casanova <jcasanov@systemguards.com.ec>

From: Jaime Casanova <jcasanov@systemguards.com.ec>
To: Andres Freund <andres@anarazel.de>
Cc: Kurt Roeckx <kurt@roeckx.be>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2021-04-07T16:28:35Z
Lists: pgsql-bugs
On Tue, Nov 10, 2020 at 05:38:08PM -0800, Andres Freund wrote:
> Hi,
> 
> On 2020-11-10 23:45:16 +0100, Kurt Roeckx wrote:
> > On Tue, Nov 10, 2020 at 08:50:39PM +0100, Kurt Roeckx wrote:
> > > > There's one known (slow) memory leak in the JIT code / LLVM. Could you
> > > > check if the issue vanishes if you disable JIT (jit = 0)?
> > > 
> > > I've just restarted it with jit = 0.
> > 
> > It's been about 3 hours since the restart, and it looks much
> > better, it seems to be solved.
> 
> Hm, darn. Any chance you could check if the leak is present if you turn
> on jit again, but disable inlining with jit_inline_above_cost=-1? If
> that still fixes the leak I think I know the issue / have a reproducer
> already...
> 

I was bit by this too while testing something.  I thought it could have been
a problem caused by the support of llvm 12? but given that this report
is for pg12, it seems this is older than that.

should we document it somewhere?

-- 
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL



Commits

  1. llvmjit: Use explicit LLVMContextRef for inlining