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 after the tab is closed. All of these things belonged to the tab but as far as I am aware, there are no other references to the original view.
I understand that nulling out references can help the garbage collector identify which objects can be collected since it doesn't need to consider one large 'island' before it can collect. I found this tool which looks like it has potential, but unfortunately is specific to Flex 3: https://code.google.com/p/flex-uicomponent-cleaner-and-gc-initiator/source/browse/trunk/com/tommyb/util/gc/UIComponentCleaner.as Does anyone know of or have anything like this for Flex 4? Marcus
