dotnet-trace CLI output doesn't update under low frequency events
Open
dotnet-trace
good first issue
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 404
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 35
Description
If you turn on dotnet-trace with a provider that's not verbose, it doesn't update the CLI window because the Task that prints to the console is stuck on the Read() call.
To repro this, try turning off SampleProfiler and just Microsoft-Windows-DotNETRuntime provider with a keyword that's not very frequent - for example, on an app that doesn't allocate anything and turn on just the GC keyword.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.