Search Issue Tracker
Won't Fix
Under Consideration for 6000.0.X
Votes
0
Found in
2021.3.36f1
2022.3.24f1
2023.2.16f1
6000.0.0b16
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-70220
Regression
No
Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
Reproduction steps:
1. Open the attached project "CrashRepro"
Expected result: Project is opened
Actual result: Editor crashes
Reproducible with: 2021.3.36f1, 2022.3.24f1, 2023.2.16f1, 6000.0.0b16
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes:
{{Failed to build mask for shadow culler. ErroCode: 3}} error is thrown before the crash
Crash is very inconsistent from 2022.2.0b1 and below, and can be reproduced by selecting multiple GameObject in the Hierarchy, switching between Scene/Game view tabs, clicking buttons or closing and reopening the project after getting the error.
First few lines of stack trace:
{noformat}0x00007FF7B907CCFD (Unity) Umbra::QueryExt::queryStaticShadowCasters
0x00007FF7B8818B87 (Unity) UmbraModule::CullShadowCastersWithUmbraThreaded
0x00007FF7B78A0047 (Unity) CullDirectionalShadowCastersJob
0x00007FF7B7B0F56D (Unity) ujob_execute_job
0x00007FF7B7B0E46D (Unity) lane_guts{noformat}
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:
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:
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.