| commit | 37825e4b3604ad66d9690f2274dc26a6ea0884ae | [log] [tgz] |
|---|---|---|
| author | Primiano Tucci <primiano@google.com> | Thu Feb 13 22:58:12 2020 +0000 |
| committer | Primiano Tucci <primiano@google.com> | Thu Feb 13 22:58:12 2020 +0000 |
| tree | 50cdffa4f2fb5a275c9e9ce41a948e7467b62cd3 | |
| parent | 40da82fa3c76a9d14bd8053d710caa01b7b200e2 [diff] |
TraceProcessor: fix trace_bounds computation The computation code was not taking into account the duration of the last slice. So in a trace like this: [ slice1 ][ slice 2 ][ slice 3 ] | | Bounds before this CL. This problem showed up only when analyzing ninja logs, where the last event went missing. Ironically this problem never shows up in most ftrace-based traces, because after every slice there is almost always a sched_wakeup event that extends the bounds to the right values. Bug: 149483774 Test: TraceProcessorIntegrationTest.TraceBounds Change-Id: I202d1c9ce105f20e40a4eb3424e76f2a773615fa
Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.
See www.perfetto.dev for docs.
See /docs/contributing.md for instructions.
The source-of-truth repo is Android's Gerrit. The GitHub repo is a read-only mirror.
You can reach us on our Discord channel. If you prefer using IRC we have an experimental Discord <> IRC bridge synced with #perfetto-dev on Freenode.