🚀 go-pugleaf

SysFreeString frees BSTR (or WideString in Delphi/BCB). But for String,
AnsiString, WideString this is done automatically. Why do you think that
memory is not released - Task Manager is not tool to detect memory leaks?

Try to execute SetProcessWorkingSetSize(GetCurrentProcess(), DWORD(-1),
DWORD(-1)) and look does this help - it will return unused memory to system.
Works for WinNT but not Win9x.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"Roberto" <roberto@dialtech.com.br> �������/�������� � �������� ���������:
news:419351d6$1@newsgroups.borland.com...
> Well,
>
> First of, I�m using BCB 5.0 Ent, W2000.
>
> I have a multithreaded software (aprox 150 threads) and one TADOConnection
> for each thread.
>
> TADOConnection *x[190];
>
> x = new TADOConnection(NULL);
>
> This array remains until the software stops.
>
> If I create one connection in design time (placing the component on the
> form), the leak appears don�t occur. But the conns cannot handle the high
> trafic of information.
>
> When I run the software in debug mode, step by step, I see the "new"
working
> and the memory grows but when the delete is called, the memory is not
> released.
>
>
> Question, when I create a String variable, I have to free this variable
too
> when the funcion terminates ??
>
> Ex:
>
> String x;
>
> x = "Test";
>
> SysFreeString(x);
>
>
> Thanks,
>
> Roberto.
>
>
> "Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message
> news:41930ae4@newsgroups.borland.com...
> > How do you detect that memory is allocated?
> >
> > //------------------------------------------
> > Regards,
> > Vassiliev V. V.
> > http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
> > ADO.Net
> > http://www.oledbdirect.com - The fastest way to access MS SQL Server,
> > MS Jet (Access) and Interbase (through OLEDB)
> >
> > "Roberto" <roberto@dialtech.com.br> �������/�������� � ��������
���������:
> > news:4192ea2e$1@newsgroups.borland.com...
> > > Friends,
> > >
> > > We are having serious trouble with ADO.
> > >
> > > Seems that after any small or huge query (Using TADOQuery dinamically
> > > created) memory remains allocated even after the "delete" command.
> > >
> > > Can anyone help ?
> > >
> > > thanks
> > >
> > > Roberto
> > >
> > >
> >
> >
>
>