I was wrong about the warning being removed in the compiler. It's still in the ApacheFlex code. Did you confirm that the module was actually leaking or just concerned about the warning? BTW the warning is only compiled into the application when the application is compiled for debug.
@Alex, do you remember this issue and if it was fixed in the Flash Player. -Darrell On Thu, Oct 31, 2013 at 12:36 PM, After24 <[email protected]> wrote: > Darrell. > > I tried differents settings in the Flex Compiler panel of the main > application property window : > > SDK 4.6, 4.10, 4.11 -> warnings show up in the console > SDK 4.5.1 -> warnings are replaced by "null" > > Do you have an idea of the way I can get rid of these warnings without > unchecking "enable warnings" in the compiler options panel ? > > Thank you. > > Vincent. > > > Le 31/10/13 16:27, Darrell Loverin a écrit : > > Does that mean that the warning shouldn't show up in the console ? >>>> >>> I means you are using a compiler that it detecting the leak scenario and >> generating the warning based on the assumed Flash Player issue. >> >> >> -Darrell >> >> >> On Thu, Oct 31, 2013 at 9:50 AM, After24 <[email protected]> wrote: >> >> Hello Darrell, >>> >>> Thank you for you answer. >>> >>> when you say >>> Darrell Loverin-2 wrote >>> >>>> So I think it is safe to ignore the warning which I believe was removed >>>> from the SDK (don't know the version) >>>> >>> Does that mean that the warning shouldn't show up in the console ? >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-flex-users.**2333346.n4.nabble.com/Memory-** >>> leaks-management-in-modules-**tp3422p3429.html<http://apache-flex-users.2333346.n4.nabble.com/Memory-leaks-management-in-modules-tp3422p3429.html> >>> Sent from the Apache Flex Users mailing list archive at Nabble.com. >>> >>> >
