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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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