Managed Thread States

Updated: May 2011

The property Thread.ThreadState provides a bit mask that indicates the thread's current state. A thread is always in at least one of the possible states in the ThreadState enumeration, and can be in multiple states at the same time.

Important
Thread state is only of interest in a few debugging scenarios. Your code should never use thread state to synchronize the activities of threads.

When you create a managed thread, it is in the ThreadState.Unstarted state. The thread remains in the Unstarted state until you call the Thread.Start method, which puts the thread into the Running state so that the operating system can schedule it for execution.

Unmanaged threads that enter the managed environment are already started. Once a thread is started, a number of actions can cause it to change states. The following table lists the actions that cause a change of state, along with the corresponding new state.

Because the Running state has a value of 0, it is not possible to perform a bit test to discover this state. Instead, the following test (in pseudo-code) can be used:

if ((state & (Unstarted | Stopped)) == 0)   // implies Running   

Threads are often in more than one state at any given time. For example, if a thread is blocked on a Monitor.Wait call and another thread calls Abort on that same thread, the thread will be in both the WaitSleepJoin and the AbortRequested states at the same time. In that case, as soon as the thread returns from the call to Wait or is interrupted, it will receive the ThreadAbortException.

Once a thread leaves the Unstarted state as the result of a call to Start, it can never return to the Unstarted state. A thread can never leave the Stopped state.

See Also

Reference

ThreadAbortException

Thread

ThreadState

Other Resources

Managed Threading

Change History