When you unload a SWF, call MyLoader.unload() or conainer.removeChild(mySwf), then logically whatever those objects contained should be closed and removed as well – automatically. To make an example, it’s like telling a person to get out of the car, and when he does there’s still a heart, lungs, kidneys, etc all just laying there in a bloody heap because, oops- you forgot to tell them to get out as well.

The point is, you shouldn’t have to explicitly get rid of everything an object contains before you get rid of the object, itself. That’s what the GC is supposed to do, and it goes to the whole point of having an object-oriented design.
Just my two cents.

sorry for replying a late. But we are loading Applications or say modules as SWFs.

Can you tell me bit more about the DOM option or any links?

Thanks for the help.

Are you playing audio, video, or streaming anything in your child swfs? Those should be closed in addition to removing your listeners.

You could also try using external interface to add and remove different swfs from the DOM, bypassing this whole loader issue.

(myLoader as Bitmap).bitmapData.dispose(); //DELETE all pixels from memory
myLoader.unload();

Yes you are right, that We should give Adobe some test application which they can see and do something positive to solve issue in next release of flash player.

About events, We are removing events but still movieclips are not being removed from the memory. In some cases we even noticed that it doesn’t remove child movieclips while you remove the parent and they are not listening to any events anymore.

I will update you guys if we find any workaround than this because in our last tests we made on the code, this trick is even not helping. Just making sure out of 1000+ classes and all movieclips in library to make sure nothing else is affecting it.

It actually require as I need to load another SWF application in place of one. If I won’t force it much, It will use some memory and while I load another application; It will double the memory usage instead of remaining at same level.

I will try to use that and see if that helps and thanks for your feedback

You mentioned listening/broadcasting events. Be sure to remove event listeners when they aren’t needed any more. That should be obvious. In cases where you need to listen to events from the stage, always use weak listeners. In fact, if you’re listening for events from object FOO in object BAR and BAR doesn’t directly manage the use of FOO (think subcomponents and similar fully-contained items), then you should be using weak listeners so that FOO doesn’t keep a reference to BAR because BAR is still listening to FOO’s events. Again, the most obvious example is the stage.