1. I think it's a matter of preference and style really. In my mind I view modules as more standalone than SWFs I might be loading otherwise. Though I rarely use modules in my programming, but I come from a more pure AS3 background so I tend to use those APIs even within Flex and stick to more GUI mockup for my flex work. 2. I've never had much difficulty with using SWFLoader, I think it's easier than modules. 3. I don't think there would be much of a difference, it all depends on where the leaks come from. You can unload a module and they even get garbage collected if you set the instance of the module to null and there are no references to it. I don't think switching to using SWFLoader will inherently cause less leaks. Have you been able to profile your application using a tool like Scout?
Kyle McKnight Senior UI Engineer - Accesso 321.347.7318 (M) On Tue, Dec 5, 2017 at 4:59 PM, aceinc <pa...@compuace.com> wrote: > I am using the Flex 3.5 SDK. > > My entire application(s) have been developed using the moduleloader and > mx:module. I am having memory leak(s) and I am trying to isolate and remove > them. > > In my research I noticed "SWFLoader" and its UnloadAndStop() method. I was > wondering if; > > 1) This would be a better choice? > > 2) It would be easy to implement? > > 3) If it would be likely to resolve my memory leak issues? > > Thanks for your help. > > > > > -- > Sent from: http://apache-flex-users.2333346.n4.nabble.com/ >
