Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.3.X
Votes
0
Found in
2018.3.0b2
Issue ID
1085304
Regression
No
GameObject.AddComponent performance severely degrades in execution time with each call when the call is inside a namespace
How to reproduce:
1. Open user-submitted project (AddComponentDegradation)
2. Open the Scene 'RuntimeTest' and enter Play Mode, observe the Console window
3. Open the Scene 'RuntimeTestWithNamespace' and enter Play Mode, observe the Console window
Expected result: performance in the 'RuntimeTestWithNamespace' scene does not degrade with each call
Actual result: performance in the 'RuntimeTestWithNamespace' scene degrades with each call
Reproducible with: 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0b5, 2019.1.0a3
Notes:
The issue can also be reproduced in a built player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
Add comment