There was a bug in flex 2.0.1 which prevented modules from getting unloaded. This was fixed by changing to weak event listeners.
If you are seeing this with flex 2.0.1, please try flex 3. Also you may want to try loading the module via the low level ModuleManager api, this should give you better control over the module. Thanks, Gaurav --- In [email protected], "Barry Evans" <[EMAIL PROTECTED]> wrote: > > Hi, > > i am having serious memory leak problems whilst using modules in flex. > The module-based application i am currently developing currently over > time kills the browser its loaded in. > > Even when i attempt to load the simplest of modules (a module with a > few buttons/empty datagrids) my flex app will eventually make > IE/Firefox fall over after consuming about 650-700MB of RAM. > > I have been reading Grant Skinner's posts on memory management and weak > reference techniques with regards to Flex/Flash player but i am still > having big problems. > > I am also attempting to figure out how to add a creationComplete event > handler on a module via actionscript. If i use the inline mxml > approach, a strong reference will be created, and i will never be able > to destroy it, resulting in the module never being removed from memory! > > Any advice and/or comments would be most appreciated, as i am hitting > brick walls here and i need to progress with haste. > > Thanks, > > Barry >
