# AS3 - tackling memory leaks

**URL:** <https://forum.kirupa.com/t/as3-tackling-memory-leaks/205711>\
**Category:** flash\
**Created:** [November 1, 2006, 6:49am UTC](https://forum.kirupa.com/t/as3-tackling-memory-leaks/205711 "2006-11-01T06:49:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ignitrix](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/ignitrix/32/2664_2.png) [@ignitrix](https://forum.kirupa.com/u/ignitrix)\
**Post date:** [November 1, 2006, 6:49am UTC](https://forum.kirupa.com/t/as3-tackling-memory-leaks/205711/1 "2006-11-01T06:49:23Z")

</div>

So I’ve been working on a fairly large, AS3 app for some time now. It has tons of graphics, sounds, animations, a couple video clips, and almost 500 external class files or so. I’m just starting to notice that after extended play, some of the animations start acting a little choppy. I’m guessing I’ve got a memory leak.

I’ve determined / tracked these down before using Valgrind, but never had a reason to track them down in an AS app. Besides the obvious “dig through the code” and “handle memory efficiently to begin with” (which I thought I had), any extra tips to tackling memory leaks in AS3?

Thanks,  
~JC
