This topic has not yet been rated - Rate this topic

ThreadPool.UnsafeQueueUserWorkItem Method

.NET Framework 4.5

Queues the specified delegate to the thread pool, but does not propagate the calling stack to the worker thread.

Namespace: System.Threading
Assembly: mscorlib (in mscorlib.dll)

public static bool UnsafeQueueUserWorkItem(
	WaitCallback callBack,
	Object state
)

Parameters

callBack: Type: System.Threading.WaitCallback
A WaitCallback that represents the delegate to invoke when a thread in the thread pool picks up the work item.

state: Type: System.Object
The object that is passed to the delegate when serviced from the thread pool.

Return Value

Type: System.Boolean
true if the method succeeds; OutOfMemoryException is thrown if the work item could not be queued.

Exceptions

Exception	Condition
SecurityException	The caller does not have the required permission.
ApplicationException	An out-of-memory condition was encountered.
OutOfMemoryException	The work item could not be queued.
ArgumentNullException	callBack is null.

Remarks

Unlike the QueueUserWorkItem method, UnsafeQueueUserWorkItem does not propagate the calling stack to the worker thread. This allows code to lose the calling stack and thereby to elevate its security privileges.

Caution
Using UnsafeQueueUserWorkItem could inadvertently open up a security hole. Code access security bases its permission checks on the permissions of all the callers on the stack. When work is queued on a thread pool thread using UnsafeQueueUserWorkItem, the stack of the thread pool thread will not have the context of the actual callers. Malicious code might be able exploit this to avoid permission checks.

Caution

Using UnsafeQueueUserWorkItem could inadvertently open up a security hole. Code access security bases its permission checks on the permissions of all the callers on the stack. When work is queued on a thread pool thread using UnsafeQueueUserWorkItem, the stack of the thread pool thread will not have the context of the actual callers. Malicious code might be able exploit this to avoid permission checks.

Version Information

.NET Framework

Supported in: 4.5, 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

.NET Framework Security

SecurityCriticalAttribute
Requires full trust for the immediate caller. This member cannot be used by partially trusted or transparent code.

Platforms

Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Reference

ThreadPool Class

System.Threading Namespace

Other Resources

The Managed Thread Pool

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)