TimeLine error about perfetto HOT 7 CLOSED

This is working as intended and comes from the fact that we automatically zoom into the region of the trace containing ftrace data (if it exists) as that's the part that most people care about.

If you zoom out, then you'll see the rest of the trace contains counters corresponding to the "linux.process_stats" data source. Because you are putting this source into a different buffer, it will naturally cover a different (larger) time range to ftrace.

from perfetto.

The trace is different of normal perfetto UI.
and what means 18:42:58 ? which time is 18:42:58 mean?
android sometime the trace timeline is normal , sometime the trace is exception

from perfetto.

The trace is different of normal perfetto UI.

That might be because the config is different to your "normal" traces. I don't see anything wrong from our side.

what means 18:42:58 ? which time is 18:42:58 mean?

The time since the start of the trace. Looks like it's been 18ish hours since the trace started.

from perfetto.

the trace only capture 60 second.
and the same config sometimes work good , sometime work wrong.
I doubt the buffer config lead to this.
can you send the issue to some people who response buffer config.

from perfetto.

@stevegolton can you ptal at this?

from perfetto.

There is a single expected frame timeline event about 19h before every other event in the trace.
Because of that the trace looks like:

[1 event].....................19 hours of nothing.......................[the rest of the trace]

We do not know why this occurs in your set up, it is not something we have encountered to my knowledge.

from perfetto.

from perfetto.