This, we can work with.
This can happen with certain arrangements of event handling.
For example, if you call SetAnimation in an End
handler, SetAnimation actually causes End
to fire, which can infinitely recurse. That can stack overflow.
This doesn't seem to be that case, but it's also likely that at some point, there was an absurd number of SetAnimation/AddAnimation calls all the same, or many of them had trackEntry.TimeScale = 0
which may have prevented them from ever ending.
Would you know if any of your code does this or something similar to this?