Search Issue Tracker
Fixed
Fixed in 2.3.1, 2.4.1, 2.5.0
Votes
2
Found in
2.3.0
2.4.0
2.5.0-pre.1
Issue ID
UUM-135935
Regression
No
Crash on UnityOpenXRMeta_XrFuncTable_ClearCachedFunc when starting, stopping and then starting Meta Quest Link using OpenXR: Meta in Play mode (every second time)
How to reproduce:
1. Create a new project using the VR template
2. Connect your XR device using Quest Link
3. Enter Play mode
4. Exit Play mode
5. Enter Play mode again
6. Observe the crash
Reproducible with: 2.4.0 (6000.5.0a7)
Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested
Reproducible on devices:
Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
Note: CQA was not able to reproduce the issue locally
First few lines of the stack trace:
0x00007FFD7B327CA6 (libUnityARFoundationMeta) UnityOpenXRMeta_XrFuncTable_ClearCachedFunc
0x00007FFD7B32E793 (libUnityARFoundationMeta) UnityOpenXRMeta_SystemProperties_IsSpatialEntitySupported
0x00007FFD7956719F (UnityOpenXR) main_UnloadOpenXRLibrary
Comments (6)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
andyb-unity
Apr 10, 2026 02:57
I have an update to share about this investigation.
First, these repro steps are incorrect and cannot produce the call stack described here. Unity OpenXR: Meta is not even installed in the VR Template, so there is no way to get a call stack from a package that isn't in the project. (Tested on Unity 6000.4.1f1)
After spending an hour trying to repro a crash with this call stack, I succeeded (although it was quite difficult for me to reproduce, and I don't understand how your code could be hitting this). I have a patch going in now that fixes the issue, which will ship in our next releases. (2.6.0-pre.1, 2.5.1, 2.4.2, 2.3.2)
These will roll out in the coming weeks. Thanks for reporting this issue to Unity!
andyb-unity
Apr 01, 2026 16:24
@FR0GG3R It's possible that we discovered and fixed a separate crash from the one you are experiencing. Meta OpenXR 2.3.1 and 2.5.0 are both live now, with 2.4.1 coming soon.
Are these the correct repro steps and callstack for the crash you are seeing? If I can repro this on my device, I'll file a new bug and post the link here so you can follow the investigation.
Fr0ggg3r
Mar 31, 2026 18:19
Is there an ETA on getting this patch out? I have the Boundary Visibility feature disable as you mention in the workaround note but this crash is still occurring.
Mackthis
Mar 26, 2026 22:55
It is definitely related to starting the subsystems after a domain reload, after some extensive and manual controlled testing.
andyb-unity
Mar 11, 2026 05:13
We have a fix for this issue in review and will get patches out as soon as we can. As an immediate workaround for anyone affected, you should be able to avoid this by disabling the Meta Quest: Boundary Visibility feature in your XR Plug-in Management settings for the Standalone build target.
DevDunk
Mar 02, 2026 16:24
For the devs trying to fix it: it being the second time might point towards domain reload. This means static values are not (un)initialized properly