ui: Embed flamegraph viewer in Heap Dump Explorer

Add a Flamegraph tab to the Heap Dump Explorer page that renders the
JAVA_HEAP_GRAPH flamegraph for the active dump using FlamegraphPanel.

The four metrics (Object Size / Object Count / Dominated Object Size /
Dominated Object Count) mirror the timeline-side flamegraph and are
parameterised on the active dump's (upid, ts) — switching dumps swaps
the data source. A single `buildMetric` helper assembles each metric
from the (table, value column, isDominator) triple it differs by, so
the four declarations stay short.

Flamegraph state (selected metric, filters, view) is held on
HeapDumpExplorerSession so it survives tab switches; reset on dump
change so the new dump opens with defaults rather than inheriting the
previous dump's filters. The setter is exposed as an arrow property
on the session and passed by reference into the FlamegraphView attrs.

Each node exposes a "Show objects from this class" action that opens a
new flamegraph-objects tab for the rows whose path_hash_stable matches
the clicked node, scoped to the active (upid, ts) — same flow used by
the timeline-side "Open in Heapdump Explorer" action. The page wires
the action to `session.openFlamegraph` directly.

A '#!/heapdump/flamegraph' subpage is added to NavState.

Change-Id: I3f55248ba09289574bd0f8aeb28c7d912f8f9951
4 files changed
tree: 75e9972cfcff98428a0a260df8afbf49138dfc0c
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. contrib/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. python/
  13. sdk/
  14. src/
  15. test/
  16. third_party/
  17. tools/
  18. ui/
  19. .bazelignore
  20. .bazelrc
  21. .bazelversion
  22. .clang-format
  23. .clang-tidy
  24. .git-blame-ignore-revs
  25. .gitallowed
  26. .gitattributes
  27. .gitignore
  28. .gn
  29. .style.yapf
  30. Android.bp
  31. Android.bp.extras
  32. BUILD
  33. BUILD.extras
  34. BUILD.gn
  35. CHANGELOG
  36. CONTRIBUTORS.txt
  37. DIR_METADATA
  38. heapprofd.rc
  39. LICENSE
  40. meson.build
  41. METADATA
  42. MODULE.bazel
  43. MODULE.bazel.lock
  44. MODULE_LICENSE_APACHE2
  45. OWNERS
  46. OWNERS.github
  47. perfetto.rc
  48. perfetto_flags.aconfig
  49. PerfettoIntegrationTests.xml
  50. persistent_cfg.pbtxt
  51. README.chromium
  52. README.md
  53. TEST_MAPPING
  54. traced_perf.rc
  55. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

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.

Core Components

Perfetto is not a single tool, but a collection of components that work together:

  • High-performance tracing daemons: For capturing tracing information from many processes on a single machine into a unified trace file.
  • Low-overhead tracing SDK: A C++17 library for direct userspace-to-userspace tracing of timings and state changes in your application.
  • Extensive OS-level probes: For capturing system-wide context on Android and Linux (e.g. scheduling states, CPU frequencies, memory profiling, callstack sampling).
  • Browser-based UI: A powerful, fully local UI for visualizing and exploring large, multi-GB traces on a timeline. It works in all major browsers, requires no installation, and can open traces from other tools.
  • SQL-based analysis library: A powerful engine that allows you to programmatically query traces using SQL to automate analysis and extract custom metrics.

Why Use Perfetto?

Perfetto was designed to be a versatile and powerful tracing system for a wide range of use cases.

  • For Android App & Platform Developers: Debug and root-cause functional and performance issues like slow startups, dropped frames (jank), animation glitches, low memory kills, and ANRs. Profile both Java/Kotlin and native C++ memory usage with heap dumps and profiles.
  • For C/C++ Developers (Linux, macOS, Windows): Use the Tracing SDK to instrument your application with custom trace points to understand its execution flow, find performance bottlenecks, and debug complex behavior. On Linux, you can also perform detailed CPU and native heap profiling.
  • For Linux Kernel & System Developers: Get deep insights into kernel behavior. Perfetto acts as an efficient userspace daemon for ftrace, allowing you to visualize scheduling, syscalls, interrupts, and custom kernel tracepoints on a timeline.
  • For Chromium Developers: Perfetto is the tracing backend for chrome://tracing. Use it to debug and root-cause issues in the browser, V8, and Blink.
  • For Performance Engineers & SREs: Analyze and visualize a wide range of profiling and tracing formats, not just Perfetto's. Use the powerful SQL interface to programmatically analyze traces from tools like Linux perf, macOS Instruments, Chrome JSON traces, and more.

Getting Started

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.

  1. New to tracing? If you're unfamiliar with concepts like tracing and profiling, start here:

  2. 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:

  3. 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:

Debian Distribution

For users interested in the Debian distribution of Perfetto, the official source of truth and packaging efforts are maintained at Debian Perfetto Salsa Repository

Community & Support

Have questions? Need help?

We follow Google's Open Source Community Guidelines.