Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2019.2.0a12
2019.2.0b3
Issue ID
1156017
Regression
Yes
[Improved Prefabs] Editor freezes with the infinite error loop after deleting the prefab with light probes when auto-bake is on
Exiting Prefab Mode pop up appears along with NullReferenceException on deleting Light Probe prefab from the project view.
Steps to Reproduce:
1. Create a new project.
2. Hierarchy > Create > Light > Light Probe Group
3. Drag and drop Light Probe Group in the project view
4. Open Light Probe Group in Prefab Mode.
5. Delete Light Probe Group prefab from Project view.
6. Select Delete from Delete selected asset popup.
Actual Result:
Exiting Prefab Mode pop up appears along with NullReferenceException and Editor breaks down
Expected Result:
Light Probe prefab gets deleted gracefully.
Note:
Refer attached video.
Reproducible on:
2019.3.0a3, 2019.2.0b3, 2019.2.0a12
Not Reproducible on:
2019.2.0a11
Environment:
Windows and MacOS
Notes:
- The issue happens only when the auto-baking is enabled in the Lighting window and doesn't happen when manual bake is on.
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
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
Resolution Note (fix version 2019.3):
Prefabs were reloaded after changes on disk. In conjunction with the LightProbeGroupInspector constantly pushing new data to be serialized, this causes an infinite loop.
This fix resolves both issues.