ADO - permanent memory leak?!
From: Michal R (michal_at_topindex.cz)
Date: 10/22/04
- Next message: Johny: "Problem with execution"
- Previous message: Viatcheslav V. Vassiliev: "Re: ADO and EOleException"
- Next in thread: Jeff Dyer: "Re: ADO - permanent memory leak?!"
- Reply: Jeff Dyer: "Re: ADO - permanent memory leak?!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 22 Oct 2004 13:16:18 +0200
Can somebode help me with ADO memory leaks?!
Problem is in a few memory object which stays in memory - detected by
MemProof:
1677 SysString 00168894 15
SysAllocStringLen(ISAUTOINCREMENT,15)
1709 SysString 00168894 15
SysAllocStringLen(ISAUTOINCREMENT,15)
1716 SysString 00168894 15
SysAllocStringLen(ISAUTOINCREMENT,15)
1723 SysString 00168894 15
SysAllocStringLen(ISAUTOINCREMENT,15)
Source module is oleaut32.dll.
When followed simple code is called in a loop, used memory by application is
still growing till...:(
A'm using D7 Prof with SP 1, Win XP and data provider is
Microsoft.Jet.OLEDB.4.0 (Access DB).
I also have tried with ODBC provider and MySQL server and problem is the
same. The only one difference is in
memory object which stays in memory (for access 22, for odbc/mysql 13).
Thanks for help, Michal R.
A have used this simple code:
------------------------------------------
procedure TForm1.specproc;
var q:TADOQuery;
begin
q:=TADOQuery.Create(nil);
try
q.SQL.Clear;
q.Connection:=ADOConnection1;
q.SQL.add('select * from mon');
q.Active:=true;
{....}
q.Active:=false;
finally
q.Free;
end;
end;
- Next message: Johny: "Problem with execution"
- Previous message: Viatcheslav V. Vassiliev: "Re: ADO and EOleException"
- Next in thread: Jeff Dyer: "Re: ADO - permanent memory leak?!"
- Reply: Jeff Dyer: "Re: ADO - permanent memory leak?!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|