Hi all,

First of all, I would like to share my admiration of your work on the Sandy project kiroukou, truly brilliant and a fantastic addition to the Flash community.

I uncovered the issue using a movie skin with a movie clip which played a four frame animation (to be placed on a box). it was set to auto update each frame. While watching the task manager i saw the memory usage start to sky rocket (I had 120 faces using this skin, so a bit of an extreme case maybe?). I found the issue to be in the TextureSkin class in the begin function. I didn't look into how it worked too much, but noticed the _tmp variable was taking on a clone of a BitmapData, but wasn't disposing the old bitmap data it held. I think i saw something by that "flashguru" guy about BitmapDatas not being deleted automatically and needing an explicit deletion to be removed from memory, so i added these two lines at 124 in TextureSkin:

_tmp.dispose();
delete _tmp;

and added a

delete _texture;

to line 94 of MovieSkin just for good measure, and it seemed to fix it up. I was tinkering with a few other things, but i think that's what fixed it up.

I've been having some z buffer issues since i did this, but they sound similiar to some of the issues posted in the forum so I will give some of those fixes a go. my particular z buffer issues may have been there before too so i dont know if there are some negative side effects of my fix; i guess you would know more about that than me.

Keep up the good work and i am really looking forward to Sandy 1.2!

This post has been edited by danielholmes: Nov 25 2006, 09:50 AM

Hi Daniel and thank you for your nice words.

Indeed the bitmapdata needs to be disposed. You're totally right.

the Z buffer problem shall be something else (IMG:style_emoticons/default/wink.gif)

Thanks for your report, and stay in the starting block for the 1.2 (IMG:style_emoticons/default/wink.gif)