Does using AfxBeginThread() require AfxEndThread()?


    Sponsored Links


  • 1. #import directive
    In my Dialog based MFC project I try to read and parse the cells of a Microsoft Excel document. Method 1) I generated a wrapper of "C:\Program Files\Microsoft Office\Office\EXCEL9.OLB" through class wizard's "add class" functionality. I got only interfaces and not the attributes of Excel related objects. So I tried Method 2. Method 2) In my dilog's header file I gave the following line #import "C:\Program Files\Microsoft Office\Office\EXCEL9.OLB" and tried compiling. This way I am able to get all the get set methods too. But I got a compilation error saying that type "_ImsoDispObj" not found. To satisy the compiler I included #import "C:\Program Files\Microsoft Office\Office\MSO9.DLL" which started giving the error type "VBEPtr" not found. I remember sometime back imported MSXML in one of my modules and it did not show up any of these dependent types. Any clues will be sincerly appreciated. Thanks and Regards, Vinodh Kumar P
  • 2. Array Manipln
    Hi i would like to know how to enter values from a file containing many records into an array ? which MFC class to use?? and how????
  • 3. resize
    How difficult is it to get a textbox to resize with a dialog box? Bear in mind I'm quite new to VC++...... Thanks guys Henry
  • 4. Excel file parsing
    Dear All, I got to open an excel file and read the cells.Is there any library avilable in SDK(VC++ 6.0)? Thanks. Vinodh Kumar P
  • 5. export global variables in DLL
    Hi, how I have to declare global variables in a dll for exporting? thanks, steffen

Re: Does using AfxBeginThread() require AfxEndThread()?

Postby Scott McPhillips [MVP] » Thu, 02 Sep 2004 08:11:06 GMT

The call to AfxEndThread is not needed and is considered harmfull.  The 
reason it is not needed is that the return 0 returns to MFC code that 
closes the thread handle.  The reason it is considered harmfull is that 
it never returns.  The thread ceases to exist during the call, and 
therefore the destructors of any objects created on the stack never get 

Scott McPhillips [VC++ MVP]

Re: Does using AfxBeginThread() require AfxEndThread()?

Postby Joseph M. Newcomer » Thu, 02 Sep 2004 23:33:06 GMT

No, and I consider using AfxEndThread to be poor programming practice. A thread should
terminate solely by returning from its top-level function. The place where you showed
AfxEndThread is pointless, because if you look at the code in MFC, you see that it will be
called almost immediately upon return anyway, but I believe that the return should never
be short-circuited.

Joseph M. Newcomer [MVP]
Web:  http://www.**--****.com/ 
MVP Tips:  http://www.**--****.com/ 

Re: Does using AfxBeginThread() require AfxEndThread()?

Postby Joseph M. Newcomer » Thu, 02 Sep 2004 23:34:29 GMT

You missed the part where I set m_bAutoDelete to FALSE before doing the ResumeThread.

Joseph M. Newcomer [MVP]
Web:  http://www.**--****.com/ 
MVP Tips:  http://www.**--****.com/ 

Re: Does using AfxBeginThread() require AfxEndThread()?

Postby Joseph M. Newcomer » Thu, 02 Sep 2004 23:35:50 GMT

ust make sure that the m_bAutoDelete is set before the ResumeThread.

On Tue, 31 Aug 2004 15:09:04 -0700, RNEELY < XXXX@XXXXX.COM > wrote:

Joseph M. Newcomer [MVP]
MVP Tips:

Similar Threads:

1.Using AfxBeginThread to create a worker thread...

Code that creates the thread...

m_pListenerThread = (CWinThread*)AfxBeginThread(
(AFX_THREADPROC)ListeningThreadFunction, (LPVOID)this );
ASSERT( m_pListenerThread );

Function that the thread is to run (code stripped out)...

UINT ListeningThreadFunction( LPVOID in_pParam )

In both Debug and Release builds, the call to AfxBeginThread hangs
infinitely in thrdcore.cpp, specifically at the function:

BOOL CWinThread::CreateThread(DWORD dwCreateFlags, UINT nStackSize,

at the WaitForSingleObject line:

VERIFY(ResumeThread() != (DWORD)-1);
VERIFY(::WaitForSingleObject(startup.hEvent, INFINITE) == WAIT_OBJECT_0);

Now, it has been a long time since I've used a worker thread as opposed to a
GUI thread and I remember that they were trivial to use...

Any suggestions why AfxBeginThread would hang itself?

BTW, the overview of how this all gets called is:

    Application calls an exposed DLL function, the DLL instantiates and
creates a series of classes to use internally, eventually the class which
needs this worker thread to 'listen' gets created.  After the class is
created, an initialization function is called on the class which creates
this thread as you see above.

    Any glaringly stupid things I'm doing/forgetting?


2.Using Afxbeginthread

I have used AfxbeginThread with ThreadProc as first argument. i wantd to ask
what is the use of second type of AfxBeginThread that takes CRunTimeClass *
as parameter..also how to use it..i mean in the first type we just have to
write our code to be executed in the thread with in that Thread function
that is passes as first argument to AfxBeginthread, but what about the other
type..where do we write our code in the second type of this API. could
someone please give me an example coz i cud'nt understand whats written in
msdn..also i didnt find any good example clearly indicating API usage with
CRunTime argument.

Thanx and Regards

Usman Jamil

3.Not understanding 'AfxEndThread'

Hello all,

   I have an app that creates a UI thread, and a worker thread to wait for 
the handle of the UI thread.   But, in the UI thread when I do a 
I get an Assert error:

In the app's view:
void CJunkThreadView::OnButton1() 
    pAnyThread = (CAnyThread*)AfxBeginThread(RUNTIME_CLASS(CAnyThread),

     //fire off a worker thread to wait for the UI's handle
     if(!(pWrkThd_1 = AfxBeginThread(WrkThread_1,this)))

    //Let the UI go
void CJunkThreadView::RunUIThread()
  pAnyThread->m_bAutoDelete = FALSE;

UINT WrkThread_1(LPVOID lParam)
    CJunkThreadView* pMe = (CJunkThreadView*)lParam;

          case WAIT_OBJECT_0:
          case WAIT_TIMEOUT:
   return 1;

 'CAnyThread' is the UI thread whose base class is CWinThread and for testing
it has only one function:
void CAnyThread::RunIt()
    AfxMessageBox("Ending Any Thread");

   /*causes assert */

   I've tried just returning from 'RunIt', which doesn't cause an assert, 
but I
don't get a ' pMe->pAnyThread->m_hThread' handle signalled in the waiting
worker thread.

   Obviously, I don't understand something? Any help appreciated.


Ray K.


4.Is there any difference between AfxEndThread and TerminateThread ?


Is there any difference between AfxEndThread and TerminateThread ? I
know we can use AfxEndThread from within the thread only but any other
difference like, cleaning up or so.. ??


5.thread never calls AfxEndThread


I have made a simple app with only one button that starts or stop a loop.
This loop is actually a thread.
In my OnInitDialog I create the thread in a suspended state and when I 
click on Start I resume the thread and when it's stop I suspend it.
Here is the code

CTestDlg* pThis;

BOOL CTestDlg::OnInitDialog()
if (!(m_pThread = AfxBeginThread(
		AfxMessageBox(_T("Cannot create thread"));
		return false;

/* static */
UINT CTestDlg::thScanCarte( LPVOID pParam )
	  pThis = (CTestDlg*) pParam;
	  return pThis->thScanCarte();

UINT CTestDlg::thScanCarte()
	USHORT status;
	CString s;
	bool bFlag = true;

		if (m_bExitThread){
			TRACE(_T("exit thread"));
	return 0;

void CTestDlg::OnClose()
	USHORT status;

	m_bExitThread = TRUE;


The problem is when my app exitI cannot see the trace 'exit thread'.
I think this code never called but why ?
When the app exits I suspend the thread so I suppose this is why
it is never called.

6. AfxEndThread problem

7. Can this be done using C#

8. Can this be done using a Data adapter??

Return to VC


Who is online

Users browsing this forum: No registered users and 41 guest