From: Andy Chandler <andrew45@bt...> - 2005-10-13 23:47:41
Now I've written the SQL heavy sections of my project, I noticed
that my exe was leaking memory slowy. I think I got all my mistakes,
but there were still bytes leaking.
Upon investigation using Memproof and Windows TaskManager, there is
some leaks on the most basic SQL statements, which is likely to be me.
This piece of code is as small of a section I could create on it's own
that generates around 24 bytes each time it's called.....
procedure TForm1.Button1Click(Sender: TObject);
row : TResultRow;
handle : integer;
handle:=db.FormatExecute('SELECT name FROM temp WHERE name=%s',['test']);
Is there anything else that needs to be free after a Query that I've
missed? A standard db.query doesn't generate the increase, but FormatExecute does.
After doing 10s of 0000's of queries, the RAM required by the
application gets significant.