I'm working on a medium-large Flex app and there I ran into 2 memory management related issues:
First - quite a bit of memory is wasted and leaks after removing UI containers from the UI as the object is never collected. Second - the ghost objects that are now removed from UI are still active or at least parts of them are and continue to respond to messages. Before going any further - I know a solution would be to manually unwatch all ChangeWatcher resulted from the BindingUtils.bindSetter that are used to cascade changes between models. However the object hierarchy rooted in the UI containers is quite deep and traverse it and calling a "destructor" for each type of object is both non- trivial and very non-elegant. Did anyone else run into similar issues? Any ideas would be extremely helpful at this point. Best regards, Sebastian
