Ok, I had heard of that: objects are not deleted by the garbage collector if there still are event listeners set up without using weakReference... But the fact is that the Timer was only a really simplified example: in the real case, each of my module is composed of a full Cairngorm stack, so I don't control most of the event listeners...
I thought unloading the module would "destroy" anything internal to this module... @valdhor: What do you mean by "Does the Flex console show that the module has unloaded?" What should I trace exactly ? Thanks for the replies ! 2009/7/17 ag_rcuren <[email protected]> > > > Could it be because you have a Timer with an event listener setup which > mean there is a reference to the Module. Wouldn't you have to first remove > the event listener so there would be no references to that module? You might > be able to use a weak reference on the listener. > > > --- In [email protected] <flexcoders%40yahoogroups.com>, > "valdhor" <valdhorli...@...> wrote: > > > > Does the Flex console show that the module has unloaded? If not, you > still have something attached to the module or the module has not released > all its resources. > > > > > > --- In [email protected] <flexcoders%40yahoogroups.com>, Julien > Nicoulaud <primo411@> wrote: > > > > > > Hi everyone. > > > > > > I have an application (a window manager) that loads modules using > > > ModuleLoader. When I unload a module, it seems it is not properly > unloaded: > > > if i setup a Timer that shows an Alert every X seconds in the module, > the > > > Alert still shows every X seconds after the module is unloaded. > > > > > > Any hints on the subject ? > > > > > > > >
