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

Поиск
Список
Период
Сортировка
От Alexander Dzuba
Тема Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq
Дата
Msg-id CAHqoriwH5uurwC1tUqUCv=M-wQohHEw5bCEJaGQDkb3-1ntugQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq  (Michael Paquier <michael@paquier.xyz>)
Список 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@sss.pgh.pa.us>:
PG Bug reporting form <noreply@postgresql.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Semab Tariq
Дата:
Сообщение: Re: Technical Support
Следующее
От: Tomas Barton
Дата:
Сообщение: Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor