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 any other 3rd party libraries or other components in your
project, which can cause mem leaks ?
-Laco.
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 error "virtual memory...".
So, I think this memory leak could be in dblib.dll or libiconv2.
Another possibility of this bug is the SQLdb itself.
If I close the program, all memory going to free. But until it is open
the memory grows up, even after ApplyUpdates and Commit.
Somebody can help me?
More info:
Lazarus 1.3 r46340M FPC 2.6.5 i386-win32-win32/win64 and SQLServer 2008.
Best regards,
Marcos Douglas
_______________________________________________
fpc-pascal maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
_______________________________________________
fpc-pascal maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
