tp: scope pprof archive members and intern their fallback mappings An archive with dozens of pprofs currently imports as an undifferentiated blob: every profile lands on the hard-coded "pprof_file" scope. Scope each profile by its source file instead: TraceFileTracker gains a CurrentFile() accessor and the pprof reader walks the file-nesting chain past the gzip layer to the nearest named ancestor. The file id is captured on the first Parse() call -- ParseProfile runs from OnPushDataToSorter, which may fire after the end-of-file notifications have popped the trace-file parsing stack, so reading CurrentFile() there would make scope attribution depend on pipeline ordering. Locations without a pprof mapping each allocated a fresh dummy mapping, so identical frames never interned across profiles and callsites multiplied by the profile count: a 32 MB / 1000-profile archive peaked at 1.8 GB and OOMed the Wasm heap. Intern the shared fallback mapping and skip re-symbolizing interned frames; the same archive now peaks at 647 MB. Diff tests lock the behaviour in: zip/tar members are scoped by member file name (walking past the unnamed gzip layer), directly opened pprofs keep the "pprof_file" scope, duplicate archive members do not duplicate frames/mappings/symbols, and mapping-less locations share a single interned "[unknown]" fallback mapping (asserted with a minimal hand-encoded pprof, since no checked-in pprof lacks mappings).
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.