AFAIK the memory management of opening and closing tiles is handled by the Mosaic framework. There is nothing that you should need to do as a tile developer.
Thanks for the answer. However, I've made a little test application (with property allowContentDelete="true"), and where I can add tiles (very simple Flex tiles, with one label and two text input).
Adding and deleting tiles multiple times made the memory goes up, and was never released (Both Firefox and IE).
It is really important for us to get the memory released, as we have many large modules that can be loaded several times.
Update: With the same application, AIR seems to do a better job, but AIR is not an option for us.
I spoke with the Developers about this issue. Unfortunately there doesn't seem to be an immediate solution:
Mosaic runs into the same flashplayer memory issues that other apps using SWFLoader experience. Mosaic 9.0.1 will include some memory optimization to help reduce the problem... [Engineering is] working ... to isolate the issues and get a fix.
I'm also facing same problem, when I remove and add tiles in the view application crashes, Is there any fix for this?
The original problem was with the Mosaic 9.0 product, and has been fixed since. If you are seeing something similar with the current release (188.8.131.52), then I suspect its another cause (although the symptoms may be similar).
Can you share the code segment that adds/removes the tile?