Thanks Alex, I had gone around and around to get a certain module to unload and was unable to determine the cause. Your article was very informative and my suspicion is that an image loaded at runtime was at fault. But that really isn't the same thing as compile-time embedded assets, is it?
As far as remote objects are concerned - if they are invoked via some sort of Command class, that should avoid this problem, am I right? Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Thursday, February 11, 2010 6:39 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Module Memory Leaks In Flex 4, styles are "per-module" and thus much less likely to leak. That's the only change. Everything else is the same. Are you seeing evidence that embedded image assets are leaking? On 2/11/10 4:24 AM, "Battershall, Jeff" <jeff.battersh...@dowjones.com> wrote: Getting modules to fully unload has been something I've spent (wasted?) a good deal of time on in the past and I've just finished reading with great interest, Alex's article on the subject: http://blogs.adobe.com/aharui/2009/08/what_we_know_about_unloading_m.html My question is - how much of this is resolved in Flex 4? Because if most or all of the issues have been addressed, I'll simply abandon my Flex 3 development of module-based applications and move to Flex 4 right now, especially given that Flex 4's release is imminent (early spring?). Of particular concern is the bit in Alex's article about unloading images and the fact that image assets could be loaded via Stylesheets, etc. Jeff Battershall Application Architect Dow Jones Indexes jeff.battersh...@dowjones.com (609) 520-5637 (p) (484) 477-9900 (c) -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
