| commit | eb64ad28d0788ddd11b34e415c94a0f3e2391bca | [log] [tgz] |
|---|---|---|
| author | Lalit Maganti <lalitm@google.com> | Tue Jun 29 00:58:44 2021 +0100 |
| committer | Lalit Maganti <lalitm@google.com> | Tue Jun 29 00:58:44 2021 +0100 |
| tree | f911c02ffb7a848854ddeadbb5670d5c92bb3184 | |
| parent | ae91e2026b7dc616d5b938557dd7bcf6c8f75d79 [diff] |
tp: handle pid reuse after explict end event This CL handles a subtle edge case which caused processes created after reuse to not be updated to the pid map. This had the affect of creating threads contiunously even when they shouldn't be. In practice, hitting this bug is extremely rare as it requires process end tracking to be active but process start tracking to *not* be active. Alternatively (and much more likely), if a process is accidentally refferred to after the process is endeded to (e.g. by a rougue ftrace event), it can cause many threads to build up unnecessarily. Bug: 192274404 Change-Id: Ie684e656a4238229690814df81b37525560c67b5
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.