Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 316 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
Can cyclic reference cause memory leaks?
Hello all,
I was looking for a solution, to handle multiple animations (multiple movie clips) for one object, based on different object states (collision, landing, etc). And ended up using cyclic reference, here is a very simple example:
As you see animations references crying and crying references animations, which again references crying, etc.
Of course it is not the only solution, I could reference to global array with animations etc, but still out of curiosity,
is it safe to use something like that? Can it cause memory leaks?
I guess it depends on implementation of garbage collector, and so far testing app didn't notice any significant memory usage outburst.
I was looking for a solution, to handle multiple animations (multiple movie clips) for one object, based on different object states (collision, landing, etc). And ended up using cyclic reference, here is a very simple example:
--for example we have couple of movie clips with animations local crying = MovieClip.new{...} local smiling = MovieClip.new{...} local hit = MovieClip.new{...} --storing references in one lua table local animations = {} animations.crying = crying animations.smiling = smiling animations.hit = hit --and to get other animations from current animation --storing lua table reference in other animations crying.other = animations smiling.other = animations hit.other = animations |
Of course it is not the only solution, I could reference to global array with animations etc, but still out of curiosity,
is it safe to use something like that? Can it cause memory leaks?
I guess it depends on implementation of garbage collector, and so far testing app didn't notice any significant memory usage outburst.
Comments
I think, your code is totally valid and harmless. Lua's garbage collector can easily handle cyclic references.