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

From: Alexander Dzuba <kaegoorn48(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-09 05:32:58
Message-ID: CAHqoriwH5uurwC1tUqUCv=M-wQohHEw5bCEJaGQDkb3-1ntugQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

ср, 8 сент. 2021 г. в 16:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > Valgrind shows static variable memory is not freed when using openssl
> > libpq/fe-secure-openssl.c:1571
> > static BIO_METHOD *my_bio_methods;
>
> > Please add a method that will free memory after use
>
> Why? It's not leaked: the struct is still available for use
> in future connection attempts.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Barton 2021-09-09 12:50:00 Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor
Previous Message Semab Tariq 2021-09-09 04:08:22 Re: Technical Support