Jump to content
Search Community

[Fixed in v3.2.1] timeline.tweenTo() causes maximum stack errors [v3.2.0]

Friebel test
Moderator Tag

Recommended Posts

Using timeline.tweenTo() is causing a range of maximum stack errors, being showed in the console. I've created a very simplified demo on codepen (see link). This looks like an issue inside version 3 to me as I follow the documentation of v3 and this demo is very reduced to just this and still shows the issue.

 

(Link to docs: https://greensock.com/docs/v3/GSAP/Timeline/tweenTo())

 

image.png.2c664cae75d855ee03d4978e247fa222.png

 

 

 

See the Pen OJVWaPM by Friksel (@Friksel) on CodePen

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

On 2/25/2020 at 6:30 PM, GreenSock said:

Yes, thanks so much for the reduced test case! And I'm so sorry about that regression. It should be resolved in the next release which you can preview at https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js

Thanks @GreenSock Jack. I just installed gsap 3.2.2 and there it's working perfectly fine without sack errors! 😀

 

[edit] Uh... I meant sTack errors, not sack errors, hahaah 😄

 

@GreenSock @ZachSaucier

  • Like 3
  • Haha 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...