We have an application that is leaking memory. Sadly, trying to diagnose this with the flex profiler (4.6, 4.7) is proving to be a frustrating experience.
I've picked on one object class to try and understand what is going on. We have a wizard-style dialog box with a sidebar control 'wizardlinks' which adds 'wizardlink' objects to it. Both are Spark group controls. The links are being added to the group with an 'addElement' call. The WizardLink instances are growing in memory and do not seem to be being released. I've pared them right down to try and eliminate possible listeners. If I immediately remove the link, Something still seems to hold on to it. If I view it in the profiler object view, it expands saying (1 Path) but won't describe what it is. Even more mysteriously - if I run with "Watch live memory data", I can see the instances going up -- but if I then do a memory dump, those instances are now missing. If I don't run with 'watch live memory data', they are there. Part of this feels like chasing shadows - are these real leaks, or just things the collector will eventually get round to?
