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)

Unity OpenXR: Meta

-

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
Log in to vote on this issue

Comments (3)

  1. 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.

  2. 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.

  3. 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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues