Hi Laco,
On Mon, Oct 20, 2014 at 2:16 AM, LacaK wrote:
> Hi Marcos,
> First useful thing would be isolate source of memory leak.
> If it is on FreePascal side, then we must search there, if it is on FreeTDS
> side, then we must report bug to FreeTDS project.
> You can use version of dblib.dll, wh
Hi Marcos,
First useful thing would be isolate source of memory leak.
If it is on FreePascal side, then we must search there, if it is on
FreeTDS side, then we must report bug to FreeTDS project.
You can use version of dblib.dll, which does not use libiconv2, so we
can isolate it.
Do you not use
On 17/10/2014 21:27, Marcos Douglas wrote:
> I have a big loop. This loop calls a INSERT script (using SQLdb) to
> insert records at a table.
> Everything works. I do not have mem-leak (heaptrc dialog is 0 unfreed)
> in my code. But the Windows "Commit charge" grows up exponential and I
> got an er
Hi,
My FPC is 2.6.5 on Windows + SQLServer 2008.
I have a big loop. This loop calls a INSERT script (using SQLdb) to
insert records at a table.
Everything works. I do not have mem-leak (heaptrc dialog is 0 unfreed)
in my code. But the Windows "Commit charge" grows up exponential and I
got an erro