Search Issue Tracker
Won't Fix
Won't Fix in 1.12.X
Votes
0
Found in [Package]
1.12.0
Issue ID
OXPB-7
Regression
No
[Oculus] SIGSEGV crash in RenderTexture::GetActive() on Quest 2
Reproduction steps:
1. Open the attached project "ReproCase.zip"
2. Switch to Android and build to Quest 1/2
3. The application crashes with release build
4. Enable "Development Build" and build again
5. Application does not crash but an exception is thrown in Android Logcat: "UnityException: GetActive can only be called from the main thread."
Expected result: Application does not hard crash with release build and exception is thrown
Actual result: Application hard crashes with release build
Reproduces on: 2019.4.35f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b6, 2022.2.0a3
Reproducible with these devices:
VLNQA00415 - Oculus Quest 2 (Quest 2), OS: 10, CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
-Release build stack trace and development build exception logs are attached named "build_release_log.txt" and "build_development_unityexception.txt" respectively
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Marking ticket as not a bug due to the error showing in editor in regards to calling RenderTexture.active outside of the main thread. Please reopen if you believe this is not the case
Resolution Note (1.12.X):
Marking ticket as not a bug due to the error showing in editor in regards to calling RenderTexture.active outside of the main thread. Please reopen if you believe this is not the case