Skip site navigation (1) Skip section navigation (2)

Re: Leak repairs

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Marko Ristola" <Marko(dot)Ristola(at)kolumbus(dot)fi>
Cc: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Leak repairs
Date: 2005-07-19 09:49:57
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC932E@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org 
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Marko Ristola
> Sent: 19 July 2005 08:37
> Cc: Anoop Kumar; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Leak repairs
> 
> 
> Have you seen this one?
> 
> 1121712844: 17186:  not freed: '0x404ef808|s1' (800 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x404f0c08|s1' (800 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x404fd008|s1' (3200 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x404fe008|s1' (3200 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x404ff008|s1' (3200 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x40500008|s1' (3200 bytes) from
> 'qresult.c:421'
> 1121712844: 17186:  not freed: '0x40501008|s1' (3200 bytes) from
> 'qresult.c:421'
> 
> Line 421 allocates a buffer into QResultClass.backend_tuples.
> 
> backend_tuples will be set into NULL in QR_Destructor() with
> "self->backend_tuples = NULL". I suspect, that the memory leak.
> 

Nicely spotted :-)

That would appear to be the last of them (at least for my simple testing
at the moment). I'll commit a patch shortly.

BTW, I assume you got that output from the VC++ debugger - care to share
how? I spent quite some time trying to persuade it to give me that and
didn't get anywhere :-(

Regards, Dave.

Responses

pgsql-odbc by date

Next:From: Marko RistolaDate: 2005-07-19 10:09:15
Subject: Re: Leak repairs
Previous:From: Marko RistolaDate: 2005-07-19 09:49:34
Subject: Re: Libpq driver: thread problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group