Search Issue Tracker
Active
Won't Fix in 2023.2.X
Votes
1
Found in
2023.2.17f1
6000.0.0b14
Issue ID
UUM-68294
Regression
No
The Editor crashes on RaiseException when Baking Probe Volumes
How to reproduce:
1. Open the “crash“ project
2. Open the “Forest_EnvironmentSample“ scene
3. Navigate to Window → Rendering → Lighting
4. On the Lighting window navigate to Probe Volumes
Expected result: The Editor continues to run
Actual result: The Editor crashes
Reproducible with: 2023.2.17f1, 6000.0.0b14
Could not test with: 2021.3.36f1, 2022.3.23f1 (errors)
Reproducible on: Windows 10 (if the device has 16GB of RAM)
Not reproducible on: Windows 10, Windows 11 (if the RAM is more than 16GB)
First few lines of Stack Trace:
0x00007FFE24B55B0C (KERNELBASE) RaiseException
0x00007FFD8E917A92 (Unity) LaunchBugReporter
0x00007FFD8E326ED7 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFD8E327A3F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFD8F022E1A (Unity) DebugStringToFilePostprocessedStacktrace
Notes:
- The exact issue could not be reproduced by CQA as the crash on our end was different
- On 2023.2.23f1 the Editor crashed with an error popup and no stack trace
- On 6000.0.0b14 the Editor crashed with a Stack Trace however, it was different from the user’s
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.