Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a12
Issue ID
1194582
Regression
Yes
[Improved Prefabs] Attempt to open broken prefab cause an error message about PreviewScene leakage
Steps:
1. Add empty GameObject to the scene
2. Make a prefab out of this GameObject
3. Delete info about GameObject in the prefab file (use OS tools for that)
4. Back to Unity Editor and double-click on the prefab asset
==>
Errors about broken prefabs are fine.
Also console has "Stage type 'UnityEditor.Experimental.SceneManagement.PrefabStage' did not clean up properly: A PreviewScene was leaked. Ensure to call 'base.CloseStage()' from your implementation of CloseStage()." error message.
Expected: The PreviewScene stage should be closed properly in case of the exception during the open prefab operation.
Please, take a look into attached movie for details.
Not repro in
Version 2018.4.9f1 (da19cd6b3373)
Version 2019.3.0b7 (82807b239940)
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