Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a1
2020.1.0a1
2020.1.0a15
Issue ID
1205313
Regression
Yes
Crash on SpookyHash::Short when continually interrupting auto-generating light
Steps to reproduce:
1. Open the attached project ("1205313.zip")
2. Open "Lights and Shadows" Scene
3. Select "Point Light", "Spot Light" and "Area Light"
4. Move the lights around the Scene continually interrupting baking
Reproducible with: 2019.3.0a1, 2019.3.0f4, 2020.1.0a1, 2020.1.0a18
Not reproducible with: 2018.4.15f1, 2019.2.17f1
First 5 lines of the stacktrace:
0x00007FF729793E4C (Unity) SpookyHash::Short
0x00007FF72A242164 (Unity) LightFalloffRefcountedDataHandle<UnityInputLightFalloffTable>::GetHash
0x00007FF72A08BF4A (Unity) SortedHashArray<LightFalloffRefcountedDataHandle<UnityInputLightFalloffTable>,DefaultHashFunctor<LightFalloffRefcountedDataHandle<UnityInputLightFalloffTable> > >::find
0x00007FF72A081A38 (Unity) EnlightenRuntimeManager::GetLightFalloffTable
0x00007FF72B9F5333 (Unity) ConvertToBakedLight
0x00007FF72B9F7F33 (Unity) CreateEnlightenBakeInputLightingJob::Execute
Notes:
- Usually crashes without a stacktrace on Windows
- Produces a full stacktrace on Mac
- Seems to only repro with URP/LWRP/HDRP set as the SRP of the Project
- Continually interrupting auto-generating light means changing the position of the lights while the light is still baking
Related to https://fogbugz.unity3d.com/f/cases/1197692/, but most likely not a duplicate.
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 2019.3):
Fixed in 2019.3.1f1