Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b12
Issue ID
786605
Regression
Yes
Instantiate, Transform and SetActive performance regression
Instantiate, Transform.parent and GameObject.SetActive all take longer than they used to in Unity 5.3.
Reproduction Steps:
1. Open the reproduction project in "case_786605-InstantiationTest.zip" in 5.3
2. Run the scene MainScene
3. Attach the Unity Profiler to the Editor
4. Press any key to run the behavior in the CubeInstantiator script
5. Note down the values in the Profiler for the custom markers
6. Repeats steps 1-5 in version 5.4
7. Compare the two sets of values, notice that 5.4 is worse
Note that these numbers are slightly better in a build, rather than in-Editor, but a performance regression still exists.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment