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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment