Google Git
Sign in
flutter/third_party/perfetto/refs/heads/dev/zezeozue/exclude_android_x
commit
8bee6a6457b9fc4003e89d4a6e2b7c2a374ec5e6
[log]
author
Zimuzo Ezeozue <zezeozue@google.com>
Fri May 22 12:20:30 2026 +0100
committer
Zimuzo Ezeozue <zezeozue@google.com>
Fri May 22 12:20:30 2026 +0100
tree
1beb44b3965f129091f9c5ae5e9a8836b0b392fc
parent
19f8a32804d4046ea0ee57103ef0ff43dd10038e [diff]
android_sdk: exclude test-only androidx host stub from perfetto_trace_lib_host_stubs

perfetto_trace_lib_host_stubs globs src/android_sdk/java/host_stubs/**/*.java,
which sweeps in androidx/test/ext/junit/runners/AndroidJUnit4.java. That stub
extends BlockJUnit4ClassRunner (org.junit.runners), but this library does not --
and should not -- depend on JUnit, so the Soong host build fails:

  host_stubs/androidx/test/ext/junit/runners/AndroidJUnit4.java:
    error: package org.junit.runners does not exist

The AndroidJUnit4 stub exists only for the standalone host runner
(tools/run_android_sdk_host_test), which compiles host_stubs with JUnit on the
classpath -- that is why it never failed there. It is not one of the SDK host
shims this library provides (dalvik annotations, SystemCleaner, android.util.*,
android.os.Process), and the Soong host/ravenwood build uses the real
androidx.test. Exclude androidx/** from the library.

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