Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
3.0.1
Issue ID
OXPB-50
Regression
Yes
[Oculus] Application crashes with signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) when RealityToolkit package is used
Reproduction steps:
1. Open the attached user's project "MyRCTTestProject.zip"
2. Switch to Android
3. Build for Quest 2
Expected result: application launches
Actual result: application crashes
Reproduces on: 2021.3.4f1, 2022.1.1f1, 2022.2.0a16
Does not reproduce on: 2020.3.34f1
Could not test on 2019.4.39f1 due to package errors when downgrading
Reproducible with these devices:
N/A, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Notes:
-The project depends on the XR Package called the RealityToolkit, which is a fork of the XRTK/MRTK. This has always worked in the Editor and on Quest 2 without fail
-Customer noted that this might be related to an issue fixed in 2021.2.14f1 (FB 1399032), which appears not to generate an error any more but still fails, as the toolkit makes use of Reflection and other functions in the .net System namespace
-Quest 2 stack trace is attached "Quest 2 Stacktrace.txt"
-Crash does not reproduce when using Oculus link
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
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
- Material Component has two horizontal lines under it when its foldouts are closed
- Some selected Mesh Renderer Materials lead to Assets folder when pinged
- Editor colors appear darkened out when HDR Display Output is enabled
Resolution Note:
We do not support RealityToolkit. This issue does not appear in XRTK or MRTK and has not been reported by other customers.