infinite loop and OOM caused by wrong passedTime about dragonbonesjs HOT 7 OPEN

one solution is to fix incorrect modification of this.time when passedTime < 0.0. but the inner processing logic is not such robust that maybe other triggers/conditions can lead to same error.

from dragonbonesjs.

for example:

// tick 1
this.time === 1000;
Date.now === 1100;
passedTime got 100;
this.time += 100;
this.time === 1100;

// change system time from 1100 to 900

// tick 2
this.time === 1100;
Date.now === 900;
passedTime got -200;
this.time -= -200;
this.time === 1300;

// tick 3
this.time === 1300;
Date.now === 901;
passedTime got -399;
this.time -= -399;
this.time === 1699;

// tick 4
this.time === 1699;
Date.now === 902;
passedTime got -796;
this.time -= -796;
this.time === 2495;

// tick N
this.time boom to Infinity
passedTime boom to -Infinity

from dragonbonesjs.

I also found the same mistake exists in the implemention of CSharp and Java, but I have not debug into the inner processing logic and I am not sure whether it will lead to infinite loop.

csharp

java

but it is ok in the implemention of CPP...(it does not use this.time to calculate the time difference automatically although this.time is wrong )

from dragonbonesjs.

thanks to @qingyangmoke 's commit fix/modifytime_2018_01_28

he fix same error when timeScale not equal to 1.0

here is PR commit 001c609

from dragonbonesjs.

clock 内部的系统时间不应该是一个递减的值，我们期望时间应该始终向前流动，所以才尝试修正负向的流逝时间，但是完全没有考虑到因此可能带来的问题，感谢提供的例子信息，我们会尝试让这个地方的逻辑更合理 ：）

from dragonbonesjs.

回复及时啊:)

烦请关注/推动对应同事关注Java，CSharp，CPP以及其他语言的对应实现问题，虽然其中CPP实现没导致坏掉。

from dragonbonesjs.

一定会将其他语言的逻辑也都统一的，请放心：）

from dragonbonesjs.