314069 2026-05-05 05:31:25 -0700 [WebXR Layers] Crashes in OpenXRLayer's endFrame() for various layer types 2026-05-07 02:30:14 -0700 1 1 1 Unclassified WebKit WebXR WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 1 svillar svillar djg kkinnunen webkit-bug-importer oldest_to_newest 2207605 0 svillar 2026-05-05 05:31:25 -0700 OpenXRxxxLayer::endFrame() crashes in releaseImage() because acquireImage() (called inside beginFrame() via populateFrameData()) was never called for that layer in the current frame. The root cause is that beginFrame() is called from inside renderLoop(), which is called from the submitFrame() dispatch. At that point activeLayerHandles contains the **previous** frame's layer list. The new layer added by applyPendingRenderState() is only reflected in activeLayerHandles when the **next** scheduleAnimationFrame() dispatch runs which is always too late. Something like this submitFrame dispatch → endFrame() → renderLoop() → beginFrame() ↑ snapshots OLD activeLayerHandles scheduleAnimationFrame dispatch → activeLayerHandles = FRESH → renderLoop() ↑ pendingFrame=true, exits early There is a clear mismatch between the layers known by WebXR and the ones used by OpenXR to render 2208109 1 svillar 2026-05-06 08:15:46 -0700 Pull request: https://github.com/WebKit/WebKit/pull/64370 2208529 2 ews-feeder 2026-05-07 02:29:39 -0700 Committed 312788@main (b0baaeaf0cd8): <https://commits.webkit.org/312788@main> Reviewed commits have been landed. Closing PR #64370 and removing active labels. 2208530 3 webkit-bug-importer 2026-05-07 02:30:14 -0700 <rdar://problem/176446755>