Search Issue Tracker
Not Reproducible
Votes
1
Found in
2018.3.0a10
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1118359
Regression
Yes
Performance regression when saving or making changes to a Prefab with lots of GameObjects
Reproduction steps:
1. Open the project inside of "prefab_regression.zip"
2. Select "Prefab Test 10000 (insanely slow)" and open it in the Prefab Editor
3. Inside of the Prefab make any change to it, such as add a component to any of the GameObjects
Expected: Prefab changes save fast
Actual: Unity takes a while to save the changes
Reproduces on: 2018.3.0a10, 2018.3.7f1, 2019.1.0b5, 2019.2.0a6
Does not reproduce on: 2017.4.20f2, 2018.3.0a9
Note:
- First noticeable degradation to performance noticeable in 2018.3.0a6, although in 2018.3.0a10 it is way more significant
Comments (1)
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
- 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
Hypertectonic
Apr 26, 2019 19:10
This happens to me also on 2018.3.12f1. Simple changes inside a prefab, like moving a gameobject inside it, or selecting another gameobject causes Unity to slow to a crawl.