microsoft / microsoft/perfview

perfcollect pid filter produces empty dump in PerfView

Open
#1,705 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
4.7k
Forks
775
Avg merge
5d 11h
Merged PRs (30d)
9

Description

# perfcollect collect sample-pid-threadtime -collectsec 10 -threadtime -pid 1
Collection started. Collection will automatically stop in 10 second(s). Press CTRL+C to stop early.

...STOPPED.

Starting post-processing. This may take some time.

Warning:
Processed 2682678 events and lost 89 chunks!

Check IO/CPU overload!

Generating native image symbol files
...FINISHED
Saving native symbols
Warning:
Processed 2682678 events and lost 89 chunks!

Check IO/CPU overload!

...FINISHED
Resolving JIT and R2R symbols
...FINISHED
Exporting perf.data file
...FINISHED
Compressing trace files
...FINISHED
Cleaning up artifacts
...FINISHED

Trace saved to sample-pid-threadtime.trace.zip

This produced a 173 MB zip file, but opening up in PerfView only shows the CPU Stack option with no content (only ROOT entry in By Name)

Ubuntu 18.04.6
perf version 4.15.18
lttng (LTTng Trace Control) 2.10.2 - KeKriek
dotnet 6.0.201
PerfView 3.03

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the perfcollect collect sample-pid-threadtime -collectsec 10 -threadtime -pid 1 command on Ubuntu 18.04.6, then open the resulting trace ZIP in PerfView 3.03 and inspect the CPU Stack view. Done means the filtered trace displays usable stack content instead of only the ROOT entry.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.