tp: partially revert "tp: remove the standalone traceconv binary" (#6973) Partial revert of https://github.com/google/perfetto/commit/2d5a0c77f71d053501ea8d6b655f7546e4ed7a82 (https://github.com/google/perfetto/pull/6410). Downstream build targets still depend on the standalone traceconv binary (e.g. //third_party/perfetto:traceconv in google3, which is breaking the autoroll), so restore it while those callers migrate to trace_processor_shell. Reverted: - src/traceconv/{main,traceconv}.cc, include/perfetto/ext/traceconv and the executable/main/traceconv_lib GN targets. src/traceconv:lib is now linked by both traceconv and trace_processor_shell. - src/traceconv/wasm_main.cc is dropped; the UI's traceconv WASM module goes back to being built from traceconv.cc. - The bundle CLI test moves back to src/traceconv/traceconv_bundle_integrationtest.cc. - Release plumbing: the LUCI recipe, package-github-release-artifacts, gen_android_bp and gen_bazel, plus the regenerated Android.bp and bazel BUILD. Not reverted: - python/tools/{cpu_profile,heap_profile}.py and the amalgamated tools/{cpu_profile,heap_profile}. https://github.com/google/perfetto/pull/6410 pointed these back at the traceconv prebuilt and its flat MODE arguments, which fixes a real issue independent of this revert: both manifests are pinned at the v57.2 release, and the v57.2 trace_processor_shell prebuilt predates the convert/util subcommands, so `trace_processor_shell util symbolize` fails against the binary the scripts download. The traceconv-name compat shim in src/trace_processor/shell is left in place: it came from https://github.com/google/perfetto/pull/6400, not https://github.com/google/perfetto/pull/6410, so trace_processor_shell keeps accepting traceconv-style command lines when invoked under that name.
Perfetto is an open-source suite of SDKs, daemons and tools which use tracing to help developers understand the behaviour of complex systems and root-cause functional and performance issues on client and embedded systems.
It is a production-grade tool that is the default tracing system for the Android operating system and the Chromium browser.
Perfetto is not a single tool, but a collection of components that work together:
Perfetto was designed to be a versatile and powerful tracing system for a wide range of use cases.
ftrace, allowing you to visualize scheduling, syscalls, interrupts, and custom kernel tracepoints on a timeline.chrome://tracing. Use it to debug and root-cause issues in the browser, V8, and Blink.We‘ve designed our documentation to guide you to the right information as quickly as possible, whether you’re a newcomer to performance analysis or an experienced developer.
New to tracing? If you're unfamiliar with concepts like tracing and profiling, start here:
Ready to dive in? Our “Getting Started” guide is the main entry point for all users. It will help you find the right tutorials and documentation for your specific needs:
Want the full overview? For a comprehensive look at what Perfetto is, why it's useful, and who uses it, see our main documentation page:
For users interested in the Debian distribution of Perfetto, the official source of truth and packaging efforts are maintained at Debian Perfetto Salsa Repository
Have questions? Need help?
We follow Google's Open Source Community Guidelines.