This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Add work item dumping support to SOS' ThreadPool command #20872
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a -wi switch to the ThreadPool command that will enumerate all queues dumping out all found work items.
For example, given this program:
Each of the A, B, C, D methods block forever, and QueueWork creates independent work for each, so ultimately we should end up with (NumProcs + 1)*4 blocked threads. However the threadpool starts with only NumProc threads, so after that the pool only adds a thread slowly (2 every second), so if we stop reasonably quickly we should see things in the threadpool queue.
Running it and quickly attaching WinDBG/sos yielded the following output:
cc: @noahfalk, @mikem8361, @kouvel