Manualreset event waitone

Starting with .NET 4.0 the framework provides a ManualResetEventSlim class to compliment the existing ManualResetEvent.ManualResetEventSlim is much more efficient for short wait times.It can be used when the event doesn't cross process boundaries so if this is the case, and you don't expect threads to be blocked for long, then ManualResetEventSlim is the better option. ManualResetEvent.WaitOne() blocks the Thread until it receives a signal. But I hope this is not really the case and the Thread is reused in background to run some other jobs because if I have more than 25 waiting threads in the queue my app is dead. Is ManualResetEvent.WaitOne() really blocking a Thread or is there any job So, wait state of a thread calling one of EventWaitHandle.WaitOne methods can end with resetting of the instance of the wait handle used in the call. (Other reasons for waking up the thread are Abort, Interrupt and, optionally, the timeout expiration). If you signal the event handle with Set, all threads in the queue will be released. WaitOne () - used to wait for the handle to be free/signalled. The exact meaning of this depends on the concrete type being used ( Mutex , AutoResetEvent or ManualResetEvent ). Close ()/Dispose () - used to release the resources used by the handle. Handle - used to get the native handle being wrapped. Most developers won't need to use this. When you run the program in ManualResetEvent mode, Thread2 will start Task1 (in Yellow color) and it'll ask you to press ENTER to pause that thread (using WaitOne()). After pressing ENTER, Thread2 will pause Task1 and control will directly shift to Main Thread where Main Thread will perform its task, in other words print numbers (in Green Color).