Thread nerver returns from WaitForSingleObject() !!!

Posted on 2000-03-22
Last Modified: 2013-12-03
I've a Mutex and 3 threads like below

HANDLE HMutex;  
bool   End = false;
void Thread_Running_1()
     WaitForSingleObejct( HMutex, INFINITE );
     // ..... do something important
  while( ! End );
void Thread_Running_2()
     WaitForSingleObejct( HMutex, INFINITE );
     // ..... do something important
  while( ! End );
//////   The main() function is only a case school
void main()
   // I create and lock the mutex

   HMutex = CreateMutex( ..... );
   WaitForSingleObejct( HMutex, INFINITE );

   // I create 2 threads and i start these threads

   CreateThread( ...., Thread_Running_1, ..... );
   CreateThread( ...., Thread_Running_2, ..... );

   // At this time, Thread 1 and 2 are in a wait state.
   // Now, We release and close the Mutex

   End = true;
   ReleaseMutex( HMutex );
   CloseHandle( HMutex );
   // At this time, the HMutex is REALLY DESTROYED

The trouble is when i release and close the Mutex handle,
only one thread will continue running. The other thread is
DEFINITELY lost. You can see the thread in "perfmon.exe".
You must call TerminateThread() api to shutdown the thread,
because the thread never returns from WaitForSingleObject().

When i close the Mutex handle, i do not know how many threads
are awaiting the mutex to be released. We could think that
the CloseHandle() will cease the WaitForSingleObject() execution
by returning WAIT_FAILED to threads but it DOES NOT.

This is same thing for Critical Section, Event, Semaphore.

How to prevent the thread from being lost ?
Question by:mars
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
LVL 22

Accepted Solution

nietod earned 100 total points
ID: 2646034
First of all, you really shoudl be using critical sections for this, not mutexes.

next you need to declare end as volatile, otherwise it may be optimized out of existance, preventing the threads from ending.  (VERY likely.)

Finally  you should not close the mutex handle unil the other threads finish.  To do this you can wait on the thread handles with WaitForSingleObject().  The wait function will return when the thread ends.  So use this to wait until two the additional threads are done, then close the mutex handle

let me know if you have any quesitons.
LVL 22

Expert Comment

ID: 2646046
One more thing the threads that lock the mutex never release it.  You should have them release the mutex before then terminate.

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This tutorial is about how to put some of your C++ program's functionality into a standard DLL, and how to make working with the EXE and the DLL simple and seamless.   We'll be using Microsoft Visual Studio 2008 and we will cut out the noise; that i…
In this article, I will show how to use the Ribbon IDs Tool Window to assign the built-in Office icons to a ribbon button.  This tool will help us to find the OfficeImageId that corresponds to our desired built-in Office icon. The tool is part of…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA.…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question