This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Chained animations lead to StackOverFlowException #5836
Milestone
Comments
ivovandongen
added a commit
that referenced
this issue
Jul 30, 2016
So, clearing the function pointer before calling it does prevent the loop leading to the StackOverFlowException. Another issue surfaces thought where the second animation is started and executed (log statements indicate so), but the visual map is not actually updated. Starting another animation does work after that. |
/sub |
Great job @ivovandongen! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In creating an activity to reproduce the error in #5721 I ran into a situation where the test app crashes due to a StackOverflowException. The relevant code in question:
Resulting in:
The actual issue is caused when cancelTransitions() is called in MapView#flyto(), which eventually reaches Transform::cancelTransition() in core where the previous
transitionFinishFn
is still set:Might be solved by clearing the
transitionFn
and then calling it. A similar situation exists in startTransition() which might instigate the loop.Possibly related: #5833
cc @tmpsantos @zugaldia
The text was updated successfully, but these errors were encountered: