Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.6f1
Issue ID
856497
Regression
No
Time to instantiate an object or add a component grows with repeated cycles
Steps to reproduce:
1. Download and open the latest attached project
2. Open the profiler window
3. Press play
Expected result: steady performance impact
Actual result: time needed to instantiate or add a component increases each time the script is run, even if you delete objects on the same frame
Reproduced on 5.2.3f1. 5.3.6f1, 5.3.7p2, 5.4.3p1, 5.5.0f3, 5.6.0a5
Notes:
-Currently the project is set to create 100 objects every frame. This can also be reproduced by lowering the number(to even 1): the time needed rises slower, but is still gets to a point where performance issues are evident.
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