Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130019
Regression
No
Crash on SendShadowCullingCallbacks when entering Play Mode with unsaved Terrain settings changes in a specific project
Steps to reproduce:
1. Open the “user’s attached project”
2. Open the “PropTests” Scene
3. Select the “3d SKYBOX TEST/Terrain” GameObject through the hierarchy
4. Open Terrain Settings under the Terrain Component through the Inspector
5. Change a couple of settings and don’t save them
6. Enter Play Mode
7. Observe the crash
Reproducible with versions: 6000.1.0a9 (last version without compiler errors), 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Couldn’t test with versions: 6000.0.64f1 (due to URP package compiler errors)
Reproducible on: macOS 15.7.2 (M1 Max), Windows 11 (user’s)
Not reproducible on: no other environment tested
Notes:
- Consistent repro when there are 5+ Terrain layers on the Terrain
- No repro when the settings changes are saved
First few lines of StackTrace:
0x00007FFAA890F30A (Unity) SendShadowCullingCallbacks
0x00007FFAA8B9A547 (Unity) PrepareDrawShadowsCommandStep1
0x00007FFAA8B96D8A (Unity) ScriptableRenderContext::ExecuteScriptableRenderLoop
0x00007FFAA8147428 (Unity) ScriptableRenderContext_CUSTOM_Submit_Internal
0x0000020EE2329DF3 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal (UnityEngine.Rendering.ScriptableRenderContext&)
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
- Search Operator Query blocks cannot be deleted using the keyboard
- Preferences window Overlay Background Color field names have no spaces between the words
- Baking APV causes crash when using Linux/ROCm/Vulkan
- Baking APV using Linux/rusticl/Vulkan generates no probes
- Baking APV with OpenGL causes "Kernel 'ClearBuffer' not found." error
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.