WebXR Immersive VR Session Startup Delay on Meta Horizon Link 207

My reports

Submit feedback

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers

Investigating

Issue

1 report

Created 6 days ago

Add your report

Suggest an edit

Copy link

Category

Link and Airlink > Other

Investigation summary

The startup of a WebXR immersive VR session in Chrome on Meta Horizon Link 207.0.0.133.434 is delayed by approximately 55 seconds due to repeated failures in creating named pipes by Meta RuntimeIPC. The failures occur because the pipe names lack the LOCAL namespace prefix required for AppContainer compatibility. This issue arises when Chrome's Isolated XR Device Service runs in an AppContainer sandbox, triggering 11-second retry cycles before xrCreateSession completes. The problem is observed with Chrome version 153.0.8010.36 and flags --force-webxr-runtime=openxr --enable-features=WebXRIncubations enabled. Disabling the sandbox with --no-sandbox allows IPC initialization to complete successfully in about 1 second without retry failures. The issue is specific to running on a Quest 3 with a Windows PC and is not resolved by flags --disable-features=XRSandbox, --disable-gpu-sandbox, --disable-utility-sandbox.