Jump to content
Search Community

Search the Community

Showing results for tags 'memory leak'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • GreenSock Forums
    • GSAP
    • Banner Animation
    • Jobs & Freelance
  • Flash / ActionScript Archive
    • GSAP (Flash)
    • Loading (Flash)
    • TransformManager (Flash)

Product Groups

  • Club GreenSock
  • TransformManager
  • Supercharge


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website



Company Website



Found 6 results

  1. fvchapa

    Memory optimize

    how is a best way to generate animate and kill then for memory optimize? im include tweenmax ang generate animation but is continued trigger and jsheap increase all time. see screen capture
  2. First of all let me thank you for your awesome loading features, what i mostly liked about them is that you can define loaders in an XML file, great job. Now to the important part. I just found out about Adobe Scout and decided to give it a try to tune my App and I found something quite weird that nearly doubled my memory use. The problem is that when i tried to decompress a loaded bitmapData with the getPixel(0,0) technique, two things used memory, Bitmap DisplayObjects and BitmapData, both used 20.480 KB. Why Bitmap DisplayObjects used memory? I thought that only BitmapData should have used memory, the Bitmap DisplayObjects was later garbage collected, but why is it being created in the first place.... So i tried using getPixel(0,0) on a clone of the bitmapData i loaded and Bitmap DisplayObjects never appeared. Is the Bitmap DisplayObjects memory being used by the ContentDisplay object that comes with the loader? If so, what can i do to prevent this from happening?
  3. I am already member of Greensock Club to purchase ThrowPorpsPlugin.js but it has memory leak issue. I have included TweenMax.js, Draggable.js, ThrowPropsPlugin.js and used this code: Draggable.create(".kr-thumb-inner", { type: 'x', edgeResistance: 0.65, bounds: '.kr-thumb-wrapper', cursor: 'pointer', dragClickables: true, throwProps: true }); Any transition didn't start so no moving element, but memory is continuously increasing. When I get rid of ThrowPropsPlugin.js, memory leak issue was gone, but It was always happen until I remove ThrowPorpsPlugin.js even I removed this option: "throwProps: true". Please check Greensock sample page itself. : https://greensock.com/throwpropsplugin It has also memory continuously increasing. You can see the page has that issue if you SHIFT + ESC in Chrome. I really need this plugin but not useful if it has such issue. Please HELP ME!
  4. Hello, I'm trying to create a simple swf loading/unloading procedure. The swf contains a document class. This is my current setup: Loading code: package projects.triveo_mobile.services.all { import com.greensock.loading.SWFLoader; import flash.display.Sprite; import flash.events.MouseEvent; /** * Loads other mobile services from the triveo platform into a single application * @author Trayko Traykoff */ public class Test extends Sprite { private var _swf_loader:SWFLoader; public function Test():void { //This is a stage movieclip close_button.visible = false; close_button.buttonMode = true; close_button.addEventListener(MouseEvent.CLICK, onCloseButton); //This is a stage movieclip load_button.buttonMode = true; load_button.addEventListener(MouseEvent.CLICK, onLoadButton); } private function onCloseButton(close_button_:MouseEvent) : void { _swf_loader.unload(); _swf_loader.dispose(true); _swf_loader = null; load_button.visible = true; close_button.visible = false; //System.pauseForGCIfCollectionImminent(0); //System.gc(); } private function onLoadButton(e:MouseEvent):void { load_button.visible = false; close_button.visible = true; _swf_loader = new SWFLoader('Untitled-1.swf', { name: 'room', container: this } ) _swf_loader.load(); } } } And this is the swf code: package projects.triveo_mobile { import flash.display.Sprite; public class MobileMainTest extends Sprite { } } Here you can see how the memory gradually progresses when I load and unload the swf: And after that i try to wait the garbage collection but the memory remains high: http://prntscr.com/5l359o I also tested this with an swf that doesn't has document class - only graphics and it also adds up apctionscript objects and overall increase in memory. Hope you can suggest something, as this seems to be the most basic setup for loading a swf. The leak is very small, but still exist and may build up.
  5. David An

    Big Memory Leak

    TweenLite.to(cloud_wrapper.find('.kr-line-timer'), openedSkyDurRemaining / 1000, { css: { width : cloud_wrapper.width() }, ease: Linear.easeNone, onComplete: function() { cloud_wrapper.find('.kr-line-timer').css('width', 0); } } ); The code above has big memory leak and memory is increasing by 1.5G for 5~6 hours and finally chrome crashes. If I remove this code, the memory leak issue is gone. cloud_wrapper has some elements has event listeners defined using jquery like following: cloud_wrapper.find('.kr-nav-arrow').on('click', function() { ... }); But it's not the object (kr-line-timer) used for TweenLite. Some people says I should remove listeners to fix memory leak issue. But If yes, when can I add the listeners again to accomplish my logic? If not, how can I fix this issue?
  6. this a testing class i did cause of have some memory issues on much, much more complicated situation i am currently in and tried this to test my memory leaks and seems MyClass instance doesnt clear it self, but tweenlite, tw is clearing from memory fine. I am just wondering if I am missing anything. I didnt even have to add any thing to stage or do any to find that instance isnt clearing when its called null. and MyClass is an empty class. public class ui extends MovieClip { private var tw:TweenLite; private var instance:MyClass; public function ui() { super(); instance = new MyClass(); tw = TweenLite.to(instance, 1, {x:10, onComplete:clearmem, onCompleteParams:[instance]}); } private function clearmem(obj:MyClass):void { if (tw != null) { tw.kill(); tw = null; } TweenLite.killTweensOf(obj); instance = null; } } I am using version 12
  • Create New...