Closed jlorich closed 9 years ago
Thanks for reporting this. It's the way the async intervals work together. The current implementation is quite fragile in that function order isn't completely deterministic. I'm working on fixing this in the next few days :+1:
I switched tabs back and forth a few times while the demo running, saw nothing, let it finish in a background tab and then wound up with this:
Looks like the loops are getting jumbled up somewhere.