🚀 go-pugleaf

My application always has finished the thread and not a loop in the process.

As my example of my coding, I suspect the line number 1:, because I thought
when I set FreeOnTerminate to true, thread should be cleared and free up
memory but the pointer of object MyThread, need it to be cleared?

If it needs to be cleared, where the code that I have to put is.

In fact the line number 1: has been called a lot of times and I thought that
it should be OK if it is a thread with using FreeOnTerminate.

Main:
1: CMyThread *MyThread = new MyThread();
2: MyThread->Resume();

3: __fastcall CMyThread::CMyThread(bool CreateSuspended)
4:            : TThread(CreateSuspended)
5: {
6:   FreeOnTerminate = true;
7: }

8: void __fastcall CMyThread::Execute(void)
9: {
10:   if (Terminated) return;

11: // Process here
12: //

13:   FreeOnTerminate = true;
14:   Terminate();
}

Sara T.

"JD" <nospam@nospam.com> wrote in message
news:40fc1022$1@newsgroups.borland.com...
>
> "Remy Lebeau \(TeamB\)" <gambit47.no.spam@no.spam.yahoo.com> wrote:
> > However, there is no leak in this case since FreeOnTerminate
> > is set to true. [...]
>
> I should have paid closer attention but the sample was so
> sparse that I ignored it, asking for more.
>
> ~ JD
>

"JD" <nospam@nospam.com> wrote in message
news:40fbf87b$1@newsgroups.borland.com...

> If you don't delete the thread when it's finished and allocate
> a new one - that's you're problem. And yes, that is a memory
> leak - a very big one at that.

However, there is no leak in this case since FreeOnTerminate is set to true.
The thread frees itself automatically when it finishes.  Now, if the thread
never finishes, that would be a problem...


Gambit