EventPipe sample profile: missing thread state information
Open
enhancement
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 404
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 35
Description
The events collected via sample profile don't provide enough information to infer the thread state. A blocked thread will have the same number of samples as one doing actual work.
If the sample profile collected only stacks from threads active on the CPUs, the lack of state information wouldn't be noticeable as it is right now. Anyway, having accurate thread state information would be helpful in this and other scenarios.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.