Instant events do not display correctly if they have the same timestamp as a duration event about perfetto HOT 3 CLOSED

In our view, this is WAI. Handling these edge cases of identical timestamps induces a high amount of complexity throughout the trace processing and UI stack and is a non issue if you use the native proto format where timestamps can be specified in nanoseconds

Basically this falls under our JSON policy (https://perfetto.dev/docs/faq#why-does-perfetto-not-support-lt-some-obscure-json-format-feature-gt-) where the cost of supporting this case does not justify the benefit.

from perfetto.

Thanks for the quick response. Would it be possible add a warning (if this occurs) somewhere in the UI then? I'm afraid this isn't obvious and even nanosecond-resolution trace formats can fall prey to this if e.g the clock's resolution is low.

In any case, JSON supports nanosecond resolution, and I already have timestamps in ns anyway, just didn't bother to plug in the support.

Thanks for the help :)

from perfetto.

Would it be possible add a warning (if this occurs) somewhere in the UI then?

From a technical perspective, yes it would certainly be possible. Would be be of a high enough priority for us to look at? Probably not: contributions for this are welcome (see https://perfetto.dev/docs/contributing/getting-started)

from perfetto.