From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Scot Loach" <sloach(at)sandvine(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: memory leak in ODBC driver |
Date: | 2004-11-27 23:19:49 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4527B5E@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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 Scot Loach
> Sent: 27 November 2004 18:11
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] memory leak in ODBC driver
>
> There is a 16-byte leak for every statement handle that has
> SQLFetch called on it.
> I have tracked this leak down to its source:
> SC_Fetch calls extend_getdata_info, which allocates memory
> for the stmt.getdata_info.
> However, this memory is never freed when the statement is deallocated.
>
> This patch seems to fix the problem - however I don't know
> enough about the internals of the driver to really understand
> if this is the correct or safe fix.
> Can one of the developers help me out here?
It certainly *looks* OK to me, but I share the same concerns as you
(I've never really got that far inside the driver before). Anyone else
care to comment?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Scot Loach | 2004-11-30 02:30:37 | Re: memory leak in ODBC driver |
Previous Message | Scot Loach | 2004-11-27 18:11:22 | memory leak in ODBC driver |