Search Issue Tracker
Fixed in 5.3.5
Votes
3
Found in
5.3.2p2
Issue ID
771609
Regression
No
Instantiating prefab with animator component for the first time causes main thread hitch
Steps to reproduce:
1) open users attached project
2) build for standalone
3) press "Spawn Direct Reference Prefab"
- note the time it took to instantiate (printed out)
4) close and run the build again
5) press "Load resources prefab" and then "Spawn resources prefab"
- notice that it took the same amount of time to Instantiate
Expected: instantiating for the first time should be quicker after loading the prefab
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
jorgenpt
Feb 18, 2016 18:46
To clarify, the issue is that spawning a prefab takes longer the first time you do it, and up to ~50ms that we cannot hide, causing frame hitches. That 3 & 5 take the same amount of time is expected, but that they take a lot longer the first time than the subsequent times is unexpected.