Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
845512
Regression
No
Unity crashes when more than one queued animation is set to enabled
To reproduce:
1. Extract "QueuedAnimationsCrash.zip".
2. Play "Test" scene.
3. In a Game window press "Crash/errors" or "Crash/errors (with weight)"
4. You should get some state.GetEnabled() errors or a Crash. (the more times you press a button, the higher chance of crashing, but usually crashes on the first click)
Expected result: enabled animations are played.
Actual result: You get state.GetEnabled() errors or a crash.
Reproducible: 5.2.3f1, 5.3.1f1, 5.4.2f2, 5.5.0b11, 5.6.0a2
Crash happens when you try to play queued animations (Animation.PlayQueued with QueueMode.CompleteOthers),
and you set more than 1 animation "enabled = true;".
Crash call stack:
output_l
vsnprintf_l
vsnprintf
VFormat
Format
Animation::CrossFade
Animation::UpdateQueuedAnimations
Animation::UpdateAnimation
AnimationManager::Update
PlayerLoop
Application::UpdateScene
Application::UpdateSceneIfNeeded
Application::TickTimer
FindMonoBinaryToUse
WinMain
strnlen
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment