Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a19
Issue ID
1210625
Regression
Yes
Crash in ProgressiveRuntimeManager::GetLightmappingGpuDevices after upgrading and opening the project
Steps to repro:
1. Download the attached project and open it.
Actual result:
Editor crashes. Last calls from the stack trace:
0x00007FF784D6CB8C (Unity) ProgressiveRuntimeManager::GetLightmappingGpuDevices
0x00007FF784BE0FF8 (Unity) Lightmapping_CUSTOM_GetLightmappingGpuDevices
0x0000013562B4EB81 (Mono JIT Code) (wrapper managed-to-native) UnityEditor.Lightmapping:GetLightmappingGpuDevices ()
0x0000013562B4DA43 (Mono JIT Code) UnityEditor.LightingWindowLightingTab:WorkflowSettingsGUI ()
0x0000013562AFF3D3 (Mono JIT Code) UnityEditor.LightingWindowLightingTab:OnGUI ()
0x0000013562AF965B (Mono JIT Code) UnityEditor.LightingWindow:OnGUI ()
Regression introduced in 2020.1.0a19,
Expected result:
Project is opened without Editor crash.
Notes:
- Reproducible in 2020.1.0a19;
- Not reproducible in 2019.3.0f4;
- Reproducible on Windows.
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
Add comment