[unixODBC-support] Memory leak in SQLFetch?

Craddock, Richard C cmi5 at cdc.gov
Tue Dec 14 18:51:05 GMT 2004


I have the same problem with easysoft's ODBC - ODBC bridge.  I am trying
to connect to postgresql as well, but I am having trouble configuring
the database.

-cameron

-----Original Message-----
From: Nick Gorham [mailto:nick.gorham at easysoft.com] 
Sent: Tuesday, December 14, 2004 12:34 PM
To: Support for the unixODBC project; Craddock, Richard C
Subject: Re: [unixODBC-support] Memory leak in SQLFetch?

Craddock, Richard C wrote:

>Here is the latest information that I have discovered.
>
>In order to detect memory leaks I run free -b before and after
executing
>my code.  I assume that the difference between the two was allocated
but
>not freed by the application.
>
>If I execute the SQLfetch() loop 101 times I get the following data:
>
>[root at localhost file_upload]# free -b
>             total       used       free     shared    buffers
>cached
>Mem:    1326329856  604139520  722190336          0  281374720
>231182336
>-/+ buffers/cache:   91582464 1234747392
>Swap:   4104372224          0 4104372224
>[root at localhost file_upload]# ./testfetch
>[root at localhost file_upload]# free -b
>             total       used       free     shared    buffers
>cached
>Mem:    1326329856  604270592  722059264          0  281391104
>231198720
>-/+ buffers/cache:   91680768 1234649088
>Swap:   4104372224          0 4104372224
>
>This shows a reproducible difference of 131072 bytes between runs.
>
>If I allow the SQLfetch() loop execute 11 times I get the following:
>  
>
Ok, there is nothing in the log that would worry me.

Can you give another driver a go ?

-- 
Nick






More information about the unixODBC-support mailing list