search

plumbee / stardust-library-plumbee

Fork of the open source Stardust library version 1.3.186. Contains bugfixes and new features.
Other
2 stars 6 forks source link

method to clear pools and reclaim memory #1

Open milkmangames opened 9 years ago

milkmangames commented 9 years ago

Is there a method to completely shutdown stardust and reclaim the memory it's consuming in object pools? When my application is completely done with stardust effects, I'd like to dispose of the engine's claimed resources entirely, but its pooling classes are all still holding references.

GuyPlumbee commented 9 years ago

Hi there, This seems strange as I've added a dispose method to the StarlingDisplayObjectPool which fires when the 'container' DisplayObjectContainer given to the Emitters particle handler is removed from the stage.

Now, on second thought, this doesn't remove references to the StarlingBitmapParticles themselves, merely calls the dispose method on them. The references however, should be cleared when the PooledStarlingDisplayObjectClass is removed from the list of initializers. Are you ever calling emitter.clearInitializers as a part of your shutdown process?

On 29 May 2015 at 20:10, milkmangames notifications@github.com wrote:

Is there a method to completely shutdown stardust and reclaim the memory it's consuming in object pools? When my application is completely done with stardust effects, I'd like to dispose of the engine's claimed resources entirely, but its pooling classes are all still holding references.

— Reply to this email directly or view it on GitHub https://github.com/plumbee/stardust-library-plumbee/issues/1.

milkmangames commented 9 years ago

Thanks Guy. Those classes don't exist in the swc I'm using, which me makes me think I'm using an old version. I'll recompile from source and report back.