Chrome ceased to display animation

[arturm65681969]

Hello!

After more than a year, Chrome ceased to display animation.

The problem does not occur on Edge, Firefox, Opera ...

http://pvcfactory.pl/Main1.html

The console shows "Main1.html: 41 Uncaught RangeError: Maximum call stack size exceeded

     At handleComplete (Main1.html: 41)

     At a.b._dispatchEvent (createjs-2015.11.26.min.js: 12)

     At a.b.dispatchEvent (createjs-2015.11.26.min.js: 12)

     At a.b._sendComplete (createjs-2015.11.26.min.js: 15)

     At a.b._loadNext (createjs-2015.11.26.min.js: 15)

     At a.b._processFinishedLoad (createjs-2015.11.26.min.js: 15)

     At a.b._handleFileComplete (createjs-2015.11.26.min.js: 15)

     At createjs-2015.11.26.min.js: 12

     At a.b._dispatchEvent (createjs-2015.11.26.min.js: 12)

     At a.b.dispatchEvent (createjs-2015.11.26.min.js: 12) "

What should I do?

Thanks in advance for the hint.

[ClayUUID · Accepted solution]

From your published output:

this.timeline.addTween(cjs.Tween.get(this.instance_19).wait(1).to({x:824.9,alpha:0.002}, 0).wait(1).to({x:824.4,alpha:0.003}, 0).wait(1).to({x:823.8,alpha:0.005}, 0).wait(1).to({x:823.3,alpha:0.007}, 0).wait(1).to({x:822.7,alpha:0.008}, 0).wait(1).to({x:822.2,alpha:0.01}, 0).wait(1).to({x:821.6,alpha:0.012}, 0).wait(1).to({x:821.1,alpha:0.013}, 0).wait(1).to({x:820.5,alpha:0.015}, 0).wait(1).to({x:820,alpha:0.017}, 0).wait(1).to({x:819.4,alpha:0.018}, 0).wait(1).to({x:818.9,alpha:0.02}, 0).wait(1).to({x:818.3,alpha:0.022}, 0).wait(1).to({x:817.8,alpha:0.023}, 0).wait(1).to({x:817.2,alpha:0.025}, 0).wait(1).to({x:816.7,alpha:0.027}, 0).wait(1).to({x:816.1,alpha:0.028}, 0).wait(1).to({x:815.6,alpha:0.03}, 0).wait(1).to({x:815,alpha:0.032}, 0).wait(1).to({x:814.5,alpha:0.033}, 0).wait(1).to({x:813.9,alpha:0.035}, 0).wait(1).to({x:813.3,alpha:0.037}, 0).wait(1).to({x:812.8,alpha:0.038}, 0).wait(1).to({x:812.2,alpha:0.04}, 0).wait(1).to({x:811.7,alpha:0.042}, 0).wait(1).to({x:811.1,alpha:0.043}, 0).wait(1).to({x:810.6,alpha:0.045}, 0).wait(1).to({x:810,alpha:0.047}, 0).wait(1).to({x:809.5,alpha:0.048}, 0).wait(1).to({x:808.9,alpha:0.05}, 0).wait(1).to({x:808.4,alpha:0.052}, 0).wait(1).to({x:807.8,alpha:0.053}, 0).wait(1).to({x:807.3,alpha:0.055}, 0).wait(1).to({x:806.7,alpha:0.057}, 0).wait(1).to({x:806.2,alpha:0.058}, 0).wait(1).to({x:805.6,alpha:0.06}, 0).wait(1).to({x:805.1,alpha:0.062}, 0).wait(1).to({x:804.5,alpha:0.063}, 0).wait(1).to({x:804,alpha:0.065}, 0).wait(1).to({x:803.4,alpha:0.067}, 0).wait(1).to({x:802.9,alpha:0.068}, 0).wait(1).to({x:802.3,alpha:0.07}, 0).wait(1).to({x:801.8,alpha:0.072}, 0).wait(1).to({x:801.2,alpha:0.073}, 0).wait(1).to({x:800.6,alpha:0.075}, 0).wait(1).to({x:800.1,alpha:0.077}, 0).wait(1).to({x:799.5,alpha:0.078}, 0).wait(1).to({x:799,alpha:0.08}, 0).wait(1).to({x:798.4,alpha:0.082}, 0).wait(1).to({x:797.9,alpha:0.083}, 0).wait(1).to({x:797.3,alpha:0.085}, 0).wait(1).to({x:796.8,alpha:0.087}, 0).wait(1).to({x:796.2,alpha:0.088}, 0).wait(1).to({x:795.7,alpha:0.09}, 0).wait(1).to({x:795.1,alpha:0.092}, 0).wait(1).to({x:794.6,alpha:0.093}, 0).wait(1).to({x:794,alpha:0.095}, 0).wait(1).to({x:793.5,alpha:0.097}, 0).wait(1).to({x:792.9,alpha:0.098}, 0).wait(1).to({x:792.4,alpha:0.1}, 0).wait(1).to({x:791.8,alpha:0.102}, 0).wait(1).to({x:791.3,alpha:0.103}, 0).wait(1).to({x:790.7,alpha:0.105}, 0).wait(1).....

IT GOES ON LIKE THAT FOR A WHILE.

Yeah, you need to stop using custom easing on your tweens. Animate CC recently added a greater selection of easing formulas; see if any of them are better for you than the default easing.

[KeelyM]

I'm having a similar issue. I'm publishing my file from animate and embedding it into Captivate as a zipped html file. When I arrive at the captivate slide with my html animation it doesn't show up and I get these errors on Chrome -

I'm not using any custom easings in my animate file. This issue only happens when testing on a web server (not locally) and it doesn't happen on mobile. Any ideas what else could cause this?