When there are animations running in a NodeGroup, the internal animations list never gets cleaned up, which means if there are constantly animations on the screen then the old ones are "leaked" (aren't removed until all animations stop)
On the leave attribute, as more animations are added, the start event is called more and more times (that is, its fired not only by the animations that are actually starting)
Similarly to #1, the end leave callback doesn't get called until all the animations stop.
Calling setState from the start leave callback causes an infinite loop.
All this makes it virtually impossible to remove animations from the DOM so as to not cause a crash.
Problem or feature description
When there are animations running in a NodeGroup, the internal animations list never gets cleaned up, which means if there are constantly animations on the screen then the old ones are "leaked" (aren't removed until all animations stop)
On the leave attribute, as more animations are added, the start event is called more and more times (that is, its fired not only by the animations that are actually starting)
Similarly to #1, the end leave callback doesn't get called until all the animations stop.
Calling setState from the start leave callback causes an infinite loop.
All this makes it virtually impossible to remove animations from the DOM so as to not cause a crash.
Steps to reproduce (only needed for problems)
Versions (only needed for problems)