Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Runtime wait-handle events capture information about wait handles. They can be useful to investigate thread pool starvation issues. For more information about how to use these events for diagnostic purposes, see logging and tracing .NET applications
WaitHandleWaitStart event
This event is emitted at the start of a wait operation on a wait handle. Here is a non-exhaustive list of managed method that could emit this event:
Monitor.WaitMonitor.Enteror the C# lock keywordManualResetEvent.WaitOneTask.Wait
| Keyword for raising the event | Level |
|---|---|
WaitHandleKeyword (0x40000000000) |
Verbose (5) |
The following table shows event information.
| Event | Event ID | Raised when |
|---|---|---|
WaitHandleWaitStart |
301 | A wait starts. |
| Field name | Data type | Description |
|---|---|---|
WaitSource |
win:UInt8 |
0x0 - Other sources.0x1 - The wait originated from managed code through the Monitor.Wait method. |
AssociatedObjectID |
win:Pointer |
Address of the associated object (for example, address of obj in the code lock(obj) {}). |
ClrInstanceID |
win:UInt16 |
Unique ID for the instance of CoreCLR. |
WaitHandleWaitStop event
This event is emitted at the end of a wait operation on a wait handle.
| Keyword for raising the event | Level |
|---|---|
WaitHandleKeyword (0x40000000000) |
Verbose (5) |
The following table shows event information.
| Event | Event ID | Raised when |
|---|---|---|
WaitHandleWaitStop |
302 | A wait stops. |
| Field name | Data type | Description |
|---|---|---|
ClrInstanceID |
win:UInt16 |
Unique ID for the instance of CoreCLR. |
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
