public inbox for [email protected]
help / color / mirror / Atom feedFrom: Igor Korot <[email protected]>
To: Tom Lane <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: How to properly fix memory leak
Date: Sat, 26 Apr 2025 16:43:27 -0500
Message-ID: <CA+FnnTy9B_CKP_PXBjZKADXaF03Nm=CcShBFCA7rjqkbcL7N6g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+FnnTyR9AoJx-3zuvgudeYmUTiNcfpAucUh0ZTcs=Ajy49qVA@mail.gmail.com>
<[email protected]>
<CA+FnnTzVntnd+RBvNQ57ZkPgKNc7HTjhxvtuELBNVcsSbZut5A@mail.gmail.com>
<[email protected]>
Hi, Tom,
On Sat, Apr 26, 2025 at 4:34 PM Tom Lane <[email protected]> wrote:
> Igor Korot <[email protected]> writes:
> >>>> auto temp1 = m_pimpl->m_myconv.from_bytes( PQgetvalue(
> >>>> res, i, 1 ) );
> >>>> m_tablespaces.push_back( temp1 );
>
> I would imagine that from_bytes() is producing a malloc'd
> string. Which part of this is responsible for seeing that
> that gets freed?
No other places produces memory leak.
And I use this function quite extensively…
Thank you.
>
> regards, tom lane
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: How to properly fix memory leak
In-Reply-To: <CA+FnnTy9B_CKP_PXBjZKADXaF03Nm=CcShBFCA7rjqkbcL7N6g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox