RESOLVED FIXED 249796
"Frame End" timeline point is wrong with UI-side compositing
https://bugs.webkit.org/show_bug.cgi?id=249796
Summary "Frame End" timeline point is wrong with UI-side compositing
Simon Fraser (smfr)
Reported 2022-12-22 11:42:52 PST
`InspectorTimelineAgent::internalStart` uses this mechanism to detect "frame end": m_frameStopObserver = makeUnique<RunLoopObserver>(static_cast<CFIndex>(RunLoopObserver::WellKnownRunLoopOrders::InspectorFrameEnd), [this]() { This doesn't work with UI-side compositing (i.e. iOS, and future macOS), because a "frame" can extend over multiple turns of the CFRunLoop while we wait for backing store flushing (see where RemoteLayerTreeDrawingArea calls didCompleteRenderingUpdateDisplay()).
Attachments
Radar WebKit Bug Importer
Comment 1 2022-12-22 11:43:10 PST
Simon Fraser (smfr)
Comment 2 2022-12-22 11:47:17 PST
Currently on iOS, "frame end" will happen before "composite end" in some cases.
Nikos Mouchtaris
Comment 3 2023-05-09 15:19:17 PDT
EWS
Comment 4 2023-05-10 12:30:11 PDT
Committed 263917@main (f11ea318b8fc): <https://commits.webkit.org/263917@main> Reviewed commits have been landed. Closing PR #13661 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.