Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.0f6
2020.1
Issue ID
1216483
Regression
Yes
Unity leaks memory/crashes when trying to open a project with a broken prefab
Steps to reproduce:
1. Attempt to open the attached project in any of the reproducible versions ("1216483.zip")
Reproducible with: 2019.3.0a1, 2019.3.1f1, 2020.1.0a23
Not reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.1.14f1, 2019.2.21f1
Workaround: Deleting the prefab lets upgrade the project. Downgrading to earlier streams and upgrading from there also seems to work sometimes.
Notes:
- Reproduces both with Asset Import Pipeline V1 and Asset Import Pipeline V2
- In the newest version, the prompt window gets stuck on Initial Asset Database Refresh
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b4
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1