Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.3.0b10
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
5. Press "Generate Lighting"
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
In Unity 2023.2 peak total memory usage grows linearly with the number of probes in your scene during a bake. Of course, this is not ideal. We suspect this is what is causing this crash.
We landed a fix in Unity 6 (aka Unity 2023.3) that ensures a constant upper bound on memory usage, no matter the number of probes.
Unfortunately, we cannot backport this to Unity 2023.2. This is partially for technical reasons and partially because tech stream releases like 2023.1 and 2023.2 were never meant to receive bug fixes once they reach end of life.
We recommend that users of 2023.1 and 2023.2 upgrade to Unity 6 to get the fix for this issue.