Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Dzuba <kaegoorn48(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq
Date: 2021-09-10 02:12:21
Message-ID: YTq/BRaH+n1MxD56@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 09, 2021 at 08:32:58AM +0300, Alexander Dzuba wrote:
> I know that this is not the real leak, but memcheck analysis shows that the
> memory was not released. Because of this, CI tests fail and deploy is
> blocked.

Perhaps there is room for improvement in valgrind.supp then?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-09-10 04:29:36 BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522)
Previous Message R. Schottland (Lowell) 2021-09-09 23:47:11 PG12 → PG13 database conversion anomaly: ERROR: function kepler_start_3(double precision, double precision) does not exist