Timeline doesn't show long frame captured in Logging

[cmkweber]

Timeline sometimes hides long frames and reports no jank detected, even when Logging reports it. Notice the frame stamps in the screenshots.

---

DevTools version: 2.21.1
Connected Device:
CPU / OS: x64 (64 bit) macos
Dart Version: 3.0.0-261.0.dev
Flutter Version: 3.8.0-15.0.pre.3 / master
Framework / Engine: 7d85a585da / 3aa112c75c
Connected app type: Flutter native (debug build)

[kenzieschmoll]

Are you still able to reproduce this? If so, is there anyway you can export the data on the Performance page and attach it to this issue so that we can reproduce?

[github-actions]

Without additional information we're not able to resolve this issue, so it will be closed at this time. You're still free to add more info and respond to any questions above, though. We'll reopen the case if you do. Thanks for your contribution!

[cmkweber]

Now that there is additional information in the FrameTiming I am able to identify the issue - the Timeline is not taking into account the vsyncOverhead - which intermittently jumps to 100ms+ (usually a few frames following a GC). The vsyncOverhead is typically very low and doesn’t contribute much to frame time except for spikes every few seconds.

[curt-weber]

This is still present using latest DevTools on stable.

Attached timeline and exported logs. If you look at Frame 7907 for example, you can see the discrepancy between the timeline and the logs. The vsyncOverhead is not being accounted for.

Logs.rtf
Timeline.json.zip