I like your humour Adrian! The loitering objects can be caused by many things. During my track down on leaks, I found out that most of the time, it was forgetting to set a property to null, not removing listeners as I expected, etc. Without seeing code, it's difficult to help you out properly. However, here are some things to ponder:
*
Allow for null values on all properties. When the null values
are received, do a clean up and release all references. This is
especially useful when you have bindings going on.
*
If you can't easily remove a listener, make it week by setting
the last parameters of AddEventListeners() to true.
*
If you are using a Dictionary, allow for weak references: new
Dictionary(true).
*
Item renderers do not release their reference to the data. You
can built a helper function that can do this for you. (See attached
file)
*
Alex Harui made a nice tutorial if you're not too familiar with
the profiler (
http://blogs.adobe.com/aharui/2008/09/using_the_flex_builder_3x_prof.htm
l)
And be patient, at the end, you'll be able (unless there's a bug) to
remove all bad references using the profiler.
Yves
CleanUp.as
Description: CleanUp.as
