Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

Alex Walker

  • Content Count

  • Joined

  • Last visited

Everything posted by Alex Walker

  1. Hi Jack, Thanks again for taking the time to look at this, I appreciate it. Answers below: 1. Are you saying that you think GSAP itself is internally keeping references to DOM elements, even when those animations are killed? Yes, I believe so. Else there is something fundamental I'm not understanding. 2. Do you see the same results when animating it without GSAP? If so, can you provide a reduced test case comparison? No, the issue does not occur when using jQuery.animate alone, without including the jquery.gsap file. See attached file JQueryTest.html 3. Do you get th
  2. Hi Jack, thank you for the advice, I've done some further testing: On inital page load - Detached DOM element count: 12 Original Test (testing within 2 seconds): Detached DOM element count: 24 Using killTweensOf() rather than .stop() and waiting 30 seconds before checking: Detached DOM element count: 24 Using killTweensOf(), setting TweenLite.autoSleep = 60; and waiting 30 seconds before checking: Detached DOM element count: 24 Used TweenMax.to, waited 30 seconds before checking: Detached DOM element count: 24 Also tested with latest jQuery 3.4.1, same res
  3. I haven't found a way to explicitly kill the tween in these circumstances as jQuery is handling it, but hopefully there is a solution. Thank you for your time!
  4. My application is quite large and the core is written in jQuery, TweenMax is used in other parts of the application, but I was hoping to take advantage of these GSAP optimisations for a specific part of it. If there isn't a fix for this I'll just revert to plain jQuery for these animations, but I'd like to know if/why there is an issue? Many thanks, Alex
  5. Hi there, I'm having an issue with GSAP creating lots of detached DOM items in chrome when a parent div is deleted during a tween, despite attempting to stop the tweens. When I do this using just JQuery and not include the GSAP plugin, no detached items remain. To view detached items in chrome I use the following under "Discover detached DOM tree memory leaks with Heap Snapshots": https://developers.google.com/web/tools/chrome-devtools/memory-problems/ Code is below, you'll need jQuery, GSAP, Tween Max and one image. 1) Check for detached items in chrome (y