flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Memory leaks management in modules
Date Sat, 02 Nov 2013 14:35:37 GMT
Is this mx TextInput or Spark?  Spark might be managing some undo stack or
something like that.

A good test is to build an AS-only equivalent and see if there is still a
problem.

-Alex

On 11/2/13 4:11 AM, "After24" <vincent@after24.net> wrote:

>Hello,
>
>I found out that the memory leak is caused by the focus manager.
>
>So concerning the warning about the module calling
>net.registerClassAlias()
>-> the module is garbage collected even when those warnings pops up in the
>console.
>
>Now I'm stuck with the focus manager causing a memory leak :
>
>After reading some blog posts about the correct way to handle module
>unloading (From Alex Harui ,Tom Sugden) I added a textInput in the shell
>application to which I give focus just before module unloading :
>Now if a module button is clicked or if  the focus is given to a textinput
>without typing anything, the module instance disappears when the run
>Garbage
>collector button is pressed but if some text is typed in a textInput the
>module stays in memory.
>I used the debugger to see if the focusManager instance keeps a reference
>to
>a module control but I don't found anything.
>
>Any idea ?
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Memory-leaks-management-in-
>modules-tp3422p3482.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.


Mime
View raw message