On 11/26/13 12:24 PM, "Carlos Rovira"
wrote:
>Hi Alex,
>
>I think bindings through MXML still leave some links that need of this
>kind
>of tool? I remember that some years ago we needed to use a similar code to
>remove all bindings in one of our MDI applications when we was about to
>close a wi
Hi Alex,
I think bindings through MXML still leave some links that need of this kind
of tool? I remember that some years ago we needed to use a similar code to
remove all bindings in one of our MDI applications when we was about to
close a window module, cleaning all the stuff generate in that mod
Interesting. I thought we got all of the leaks out of binding. Do you
know what actually had to get cleaned to clean up the memory?
-Alex
On 11/26/13 7:24 AM, "Marcus Wilkinson" wrote:
>So just to follow up. I hacked up the UIComponentCleaner so that is will
>work with IVisualElementContainer
So just to follow up. I hacked up the UIComponentCleaner so that is will
work with IVisualElementContainers. The code is far from perfect, but it
seems to work for now:
http://pastebin.com/cxcSWGNK
I intend to do a cleaner version of this when I have time and to host it in
GitHub, but i'm just usi
So we have a tabbed application where a memory leak of about 5MB doesn't
seem to be collected properly. I am looking for an easy way out to help out
the GC. After using the flash builder profiler it seems that lots of
bindings amongst visual components and other things are still hanging
around afte
