Search Issue Tracker
Third Party Issue
Third Party Issue in 1.16.X
Votes
0
Found in [Package]
1.16.0-pre.1
Issue ID
OXRB-626
Regression
No
Crash on UnityEngine.SubsystemBindings:DestroySubsystem when Meta XR Simulator is enabled
How to reproduce:
1. Open the attached project "IN-113490"
2. Enable Meta XR Simulator
3. Enter Play mode
4. Observe the crash
Expected result: Meta XR Simulator opens
Actual result: Unity crashes
Reproducible with: 1.13.0 (6000.3.0a6), 1.16.0-pre.1 (2023.1.0b1, 6000.0.55f1, 6000.2.0f1 (eed1c594c913), 6000.3.0a6)
Could not test with: 1.10.0 (6000.3.0a6) (below minimum OpenXR version), 1.16.0-pre.1 (2023.1.0a1) (Meta XR Simulator package errors)
Reproducible on: macOS Sequoia 15.3
Not reproducible on: Windows 11 Enterprise
Notes:
-Reproducible with Meta XR Simulator 77.0.0
-Crash only occurs 1st time after opening the project
First few lines of the stack trace:
at <unknown> <0xffffffff>
at UnityEngine.SubsystemBindings:DestroySubsystem <0x00007>
at UnityEngine.IntegratedSubsystem:Destroy <0x00027>
at UnityEngine.XR.Management.XRLoaderHelper:DestroySubsystem <0x000a3>
at UnityEngine.XR.OpenXR.OpenXRLoaderBase:DestroySubsystem <0x00023>
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
We have investigated this issue and believe that it is caused by the V77 Meta XR Simulator version. We have reported this issue to our partners at Meta for resolution. Please revert to V76 Meta XR Simulator or lower to avoid this issue.
Resolution Note (1.16.X):
We have investigated this issue and believe that it is caused by the V77 Meta XR Simulator version. We have reported this issue to our partners at Meta for resolution. Please revert to V76 Meta XR Simulator or lower to avoid this issue.