My reports
Submit feedback
WebXR Session Hang on Quest Browser with MSAA, Per-Frame Shadow Pass, and 3D Gaussian Splatting
Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers
Investigating
Issue
1 reportCreated 5 days ago1
Add your report
Subscribe
Suggest an edit
Copy link
Category
Graphics
Investigation summary
A WebXR session in Quest Browser hangs permanently when combining MSAA (antialias: true), per-frame shadow map rendering (three.js shadowMap with autoUpdate enabled), and the Spark 3D Gaussian Splatting renderer (using fenceSync and getBufferSubData for async GPU readbacks). This issue occurs on Quest 3, is reproducible with three.js 0.185.1 and @sparkjsdev/spark 2.1.0, and does not occur on desktop Chrome, PICO 4, or Apple Vision Pro. The hang happens within ~2 seconds without a webglcontextlost event or GPU process recovery, and the browser fails to trigger context loss recovery, leaving the XR session frozen while the headset OS remains responsive.
Still need help?
Tell us what you need support with and we'll find the best solution for you.Get support
Get answers from the community
If you're having trouble, find answers to your questions from Meta Quest users around the world.Go to community forum
Virtual reality / Meta Horizon
Support and legal
Virtual reality / Meta Horizon
Support and legal
Virtual reality / Meta Horizon
Support and legal
English (US)
© 2026 Meta