[Webkit-unassigned] [Bug 249796] New: "Frame End" timeline point is wrong with UI-side compositing
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 22 11:42:52 PST 2022
https://bugs.webkit.org/show_bug.cgi?id=249796
Bug ID: 249796
Summary: "Frame End" timeline point is wrong with UI-side
compositing
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Web Inspector
Assignee: webkit-unassigned at lists.webkit.org
Reporter: simon.fraser at apple.com
CC: inspector-bugzilla-changes at group.apple.com
`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()).
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221222/14fc5fff/attachment.htm>
More information about the webkit-unassigned
mailing list