Files
TheRock/rocm-systems/projects/rocprofiler-sdk/external/perfetto/docs/faq.md
T
derek.holloway 7502bf64a4
CodeQL / Analyze (actions) (push) Canceled after 0s
CodeQL / Analyze (python) (push) Canceled after 0s
pre-commit / pre-commit (push) Canceled after 0s
Multi-Arch CI / setup (push) Canceled after 0s
Publish build_manylinux_x86_64 images / publish_build_manylinux_x86_64 (push) Canceled after 0s
Setup (Multi-Arch) / setup (push) Canceled after 0s
Multi-Arch CI / Linux::${{ fromJSON(needs.setup.outputs.linux_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubi10 image / publish_no_rocm_image_ubi10 (push) Canceled after 0s
Multi-Arch CI / Windows::${{ fromJSON(needs.setup.outputs.windows_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Multi-Arch CI / Manifest Diff (push) Canceled after 0s
TheRock Manifest Diff Report / Generate Manifest Diff Report (push) Canceled after 0s
Multi-Arch CI / CI Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_ocl_rt images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_rocgdb images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Unit Tests / Unit Tests :: ubuntu-24.04 (push) Canceled after 0s
Unit Tests / Unit Tests :: windows-2022 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_media (push) Canceled after 0s
Unit Tests / Unit Tests Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_openmpi (push) Canceled after 0s
Flatten subprojects into a single base monorepo
2026-09-02 16:34:47 -07:00

2.9 KiB

Frequently Asked Questions

How do I open trace in UI from command line?

When collecting traces from the command line, a convenient way to open traces is to use the open_trace_in_ui script.

This can be used as follows:

curl -OL https://github.com/google/perfetto/raw/master/tools/open_trace_in_ui
chmod +x open_trace_in_ui
./open_trace_in_ui -i /path/to/trace

If you already have a Perfetto checkout, the first two steps can be skipped. From the Perfetto root, run:

tools/open_trace_in_ui -i /path/to/trace

Why does Perfetto not support <some obscure JSON format feature>?

The JSON trace format is considered a legacy trace format and is supported on a best-effort basis. While we try our best to maintain compatibility with the chrome://tracing UI and the format spec in how events are parsed and displayed, this is not always possible. This is especially the case for traces which are programmatically generated outside of Chrome and depend on the implementation details of chrome://tracing.

If supporting a feature would introduce a misproportional amount of technical debt, we generally make the choice not to support that feature. Users are recommended to emit TrackEvent instead, Perfetto's native trace format. See this guide for how common JSON events can be represented using TrackEvent.

Why are overlapping events in JSON traces not displayed correctly?

The Perfetto UI and trace processor do not support overlapping B/E/X events, in compliance with the JSON spec. As stated in the spec, events are only allowed to perfecty nest.

Users are recommended to emit TrackEvent instead, Perfetto's native trace format. See this guide for how common JSON events can be represented using TrackEvent.

How can I use Perfetto tooling without instrumenting my program?

A common problem is that users want to use Perfetto analysis and visualization tooling but they don't want to instrument their program. This can be because Perfetto is not a good fit for their use-case or because they may already have an existing tracing system.

The recommended approach for this is to emit Perfetto's native TrackEvent proto format. A reference guide for this is available here.

My app has multiple processes. How can see all of them in the same trace?

Use the Tracing SDK in "system mode". All processes will connect to traced over a socket and traced will emit one trace with all processes.