commit | da5ae11248810b4e3391feb185a359ae1ffb475c | [log] [tgz] |
---|---|---|
author | Aaron Vaage <vaage@google.com> | Tue Apr 23 10:33:46 2024 -0700 |
committer | Aaron Vaage <vaage@google.com> | Tue Apr 23 10:33:46 2024 -0700 |
tree | 9a008727f45c204b47d629aecdd3507325ce246f | |
parent | a4b6bc3ece4d03e16817cdfcadbd5e6945645552 [diff] |
Trace Redaction - Frame Timeline Screen updates are communicated using frame_timeline_event packets. These packets fall into one of five types: 1. expected display frame start (pid + cookie) 2. actual display frame start (pid + cookie) 3. expected surface frame end (pid + cookie) 4. expected surface frame end (pid + cookie) 5. frame end (cookie) Start events are end events are connected through their cookie values. Because cookie saves are unique across the whole trace, it is safe to assume that 'frame end' with cookie C matches 'frame start' with cookie C.` Frame events will appears for a little number of processes. They always appear for surface flinger, and they will optionally appear with an app. As implemented, only events from the target package are retained. Bug: 333404689 Change-Id: Iabff83549874f1bfbd3875d2ae3cff1a26b68e83
Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.
See https://perfetto.dev/docs or the /docs/ directory for documentation.