In our testing properly cleaned up modules unload. You cannot use System.totalMemory to determine if the module unloads. Modules that bring in style declarations for components not in the main app stick in memory because they get registered with the StyleManager. In such a case, the styles should be brought into the main applicationDomain via external CSS module or by putting the styles in the main app. You must use the profiler to find out what is hanging onto the objects in the module. If you find a case where something is hanging on, file it as a bug. We will not make force unloading of modules the default behavior any time soon.
Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of grg_blls Sent: Thursday, March 26, 2009 3:39 AM To: [email protected] Subject: [flexcoders] Re: Issue with Modules unloading... Hi all, I have a similar thread ("A module loading issue" still open in the forum) of the issue I have while loading modules...(!) As this issue here is obviously in the same context, I did check with my application the memory usage after unloading any previously loaded module. Nothing seems to get garbage collected and no memory is released - as was already described here. Loading any other module next, memory usage grows accordingly. I post this as my modules don't contain any animations, just plain vanilla TabNavigators, Accordions, Canvas, other regular controls stuff, plus some gif images. Whatever I tried (including what was described here in the beggining of the thread) memory usage just keeps growing. I only hope for the new version handling modules in a proper way, as I can't see anything that can be done with current version. Thanks all George --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, "Battershall, Jeff" <jeff.battersh...@...> wrote: > > Alex, > > I have a question - the bugbase entry referred to by Vito focuses on > animation - what about plain jane embeded images? Also, is there a > general timeframe for Flex 3.4? > > Jeff > > -----Original Message----- > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On > Behalf Of Alex Harui > Sent: Tuesday, March 24, 2009 2:05 PM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: RE: [flexcoders] Issue with Modules unloading... > > > > It is scheduled for Flex 3.4 > > > > Alex Harui > > Flex SDK Developer > > Adobe Systems Inc. <http://www.adobe.com/> > > Blog: http://blogs.adobe.com/aharui > <http://blogs.adobe.com/aharui> > > > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On > Behalf Of cuttenv > Sent: Tuesday, March 24, 2009 2:51 AM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Issue with Modules unloading... > > > > Hello, > I had an issue with Modules unloading, especially ones that had > embedded images or animations playing in them. I am still convinced that > ANY Module has a hard time being unloaded from memory. I was wondering > if anyone had a sound solution to fixing this issue or ran into it > before. I also wanted to encourage you guys to vote on this issue > because it has been open since last August. I am pretty disappointed > with the current state of Modules in Flex, but I hope it can be fixed > soon. > http://bugs.adobe.com/jira/browse/SDK-16613 > -Vito >
