I have been working using the profiler for the last several days trying to resolve some serious memory issues with our application.
I am interested in hearing from others who have used the profiler and if they are seeing the same issues as we are. Our application is mainly structured as a series of TitleWindow's that each contain a Module. The problem has been Modules that don't get GC'd. Of course we went after the obvious thing like making listener's use weakReferences and generaly reviewing our code but when that didnt resolve the problem we dug deeper. What we noticed was that certain controls seemed to prevent the Module from being GC'd. In the end we tried a completely empty Module, just opening/closing tags in mxml and then added simple tags without any attribute or binding to complicate things. So we got to several VBox/HBox/Form/FormItem/Label and everything is fine, you close and the Module is GC'd. But then the first "problem" control we hit was the TextArea. Add that to the mix and the Module wont be GC'd, remove it and it does. Same with DataGrid. Same with any mxml component (even an empty mxml component) We are pretty surprised that basic framework control are causing problems, we expected our own to cause issues or our bad code but not framework controls. Anyone used the profiler and seen this sort of problem? tks
