Re: How to properly fix memory leak - Mailing list pgsql-general

From Laurenz Albe
Subject Re: How to properly fix memory leak
Date
Msg-id 0a2be546e57d6088acf734f8d6a308a984e7171b.camel@cybertec.at
Whole thread Raw
In response to How to properly fix memory leak  (Igor Korot <ikorot01@gmail.com>)
Responses Re: How to properly fix memory leak
List pgsql-general
On Fri, 2025-04-25 at 22:24 -0500, Igor Korot wrote:
> Hi, ALL,
>
> [code]
>     auto res = PQexec( m_db, m_pimpl->m_myconv.to_bytes( query.c_str()
> ).c_str() );      /* ask for binary results */
>     if( PQresultStatus( res ) != PGRES_TUPLES_OK )
>     {
>         auto err = m_pimpl->m_myconv.from_bytes( PQerrorMessage( m_db ) );
>         errorMsg.push_back( L"Update validation table: " + err );
>         result = 1;
>     }
>     else
>     {
>         for( int i = 0; i < PQntuples( res ); i++ )
>         {
>             auto temp1 = m_pimpl->m_myconv.from_bytes( PQgetvalue(
> res, i, 1 ) );
>             m_tablespaces.push_back( temp1 );
>         } // this line gives a leak according to VLD
>     }
>     PQclear( res );
>     return result;
> [/code]
>
> I ran this code on MSVC 2017  with VLD and according to the VLD report I have
> a memory leak on the line indicated.
>
> Should I call PQclear() on every iteration of the loop?
>
> And I hope I handle the error cae properly...

No, PQclear() would cause an error (double free).

If it is not a spurious complaint, the leak would have to be in m_tablespaces.push_back().

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Igor Korot
Date:
Subject: Re: How to properly fix memory leak
Next
From: Igor Korot
Date:
Subject: Re: How to properly fix memory leak