Hi there,

Our project, wich needs to be deployed 24/7 in lots of terminals, is experiencing a big memory leak.
Would like to know about best practices to trackdown solve memory leaks in Director Projects.

Let me explain a little what occurs. We have a project with several movies and a MIAW. Whenever we stop any of those movies (inside the IDE) and play it again or pass from a movie to another using 'go to the movie' the projector claims for 200k extra (more or less). Let's say the projector is at movie 1 and we pass to movie 2, then back to 1, movie 1 demands 200k extra RAM; if we move forward to movie 2 it demands sums ups 200k more. After a little navigation the RAM comsuption goes really high !

The way we build up the interface is loading an external XML using a Flash XML object for each movie, parsing it and starting the generation of new members and managing puppet sprites according to the interface descriptive information found in the XML, so that there is a lot of iteration through the XML nodes.

The project is very OOP oriented, and we manage quite a few parent scripts, and are attaching and deattaching behaviors to some sprites on runtime.

I have read that almost any object in Lingo is a door open to a memory leak (lists, script instances, etc). I believe that Director should be garbage collecting any object when closing a movie an opening another with 'go to the movie'. How can we make sure that the objects are garbage collected ???

Also we fear that sprites be not cleaned up and that they raise in memory consumption.

I believe the problem might be coming from three ways :

Flash XML Object load method memory leak ?
references to objects not set to Void when the movie stops ? - would it make a diffference ?
Data stored in sprite channels not cleaned up. ? how to clean them up ?

Is there any way to *force* Director to garbage collect every object but globals at a given time ?

We need to stop these memory leak in 3 or 4 days. Any advise would be much appreciated.


Bests

Sergio