<div>
I believe this is the reason<br />
<br />
when AfxEndThread is called it deallocates the objects on the stack - however It does not call thier destructors and CString does not deallocate the memory it allocated to store the string hence a leak
</div>


<div>
Hi,<br />
Should I use AfxEndThread(1) or return 1 to exit a thread prematurely?
</div>


<div>
personally I only use AfxEndThread when I need to exit a thread quickly due to a serious problem or situation (ie if I did try to close the thread cleany it would crash). otherwise I just return with a relevent error code. 
</div>


<div>
<div class="content wysiwyg-content">
I have a worker thread running. I have a CString object created on stack frame. When I exit the thread prematurely, using AfxEndThread(1) I get memory leaks in debug window. But if I do a return 1, I do not get any memory leaks . Why?
</div>
</div>


I have a worker thread running. I have a CString object created on stack frame. When I exit the thread prematurely, using AfxEndThread(1) I get memory leaks in debug window. But if I do a return 1, I do not get any memory leaks . Why?

I believe this is the reason

when AfxEndThread is called it deallocates the objects on the stack - however It does not call thier destructors and CString does not deallocate the memory it allocated to store the string hence a leak

Hi,
Should I use AfxEndThread(1) or return 1 to exit a thread prematurely?

personally I only use AfxEndThread when I need to exit a thread quickly due to a serious problem or situation (ie if I did try to close the thread cleany it would crash). otherwise I just return with a relevent error code. 

AfxEndThread causes memory leaks

Kernel and system programming is the process of creating the software necessary for a computer or device to function and operate other programs. Some operating systems (such as Microsoft Windows) are proprietary, but others, such as the various Linux distributions, are open source.