🚀 go-pugleaf

"Mark Roberts" <markr@piracle.com> wrote in message 
news:47349c3a$1@newsgroups.borland.com...

> As I watch the Processes screen of the Task Manager I see
> the process continually growing as the clients connect and
> disconnect.

Task Manager is a very poor way to measure leaking.  Borland/CodeGear's 
memory manager does not release freed memory back to the OS right away.  It 
is cached for later re-use.  Task Manager has no way of knowing that.  All 
it shows is how much memory is allocated to the process, but not how the 
process is actually using the memory.

> I'm calling AThread->Connection->Disconnect in the
> OnExcute function

That is fine.

> AThread->StopMode = smTerminate;
>
> AThread->Stop();
>
> TCPServer->ThreadMgr->ReleaseThread(AThread);
>
> TCPServer->ThreadMgr->TerminateThreads(TCPServer->ThreadMgr->ActiveThreads);
>
> in the OnDisconnect function.

Do not do ANY of that!  Especially NOT in the OnDisconnect event!  The 
thread is still active inside that event.  It can't be released yet.  Let 
TIdTCPServer do all of the thread management for you.


Gambit