Here is how we manage collection when it comes to Araay collection.
We declare a custom class whic helds an instance of the array
collection and an array for fast searching.
[Bindable]
public class FullGameHistorySuiteStatuses
{
private var _suiteStatusesArrayCollection : ArrayCollection = new
i've tried your example and didn't notice any memory leakage.
anyway, why do you need to create components and remove them, and
create again the same components? It looks like you made up an
artificial problem for yourself :)
--- In flexcoders@yahoogroups.com, e_baggg [EMAIL PROTECTED] wrote:
My original mxml was a bad example I guess. In my application, which
is a Flex app that has its own windowing (exactly like Windows)...when
I add and create Windows and close them, the browser CPU memory always
increments (except for IE when I minimize the browswer window and
memory is
i still think that you could re-use window instances. After all, how
many windows a regular human being is capable to deal with at one time
- 7, 12,25? You just create a pool of instances and there will be
*zero* startup time for the window and *zero* memory increase.
Otherwise, you would need to
Setting Image to null is not good enough. Call load(null) on the Image before
removing it from the display list and releasing references to it.
GC() is not deterministic. The only ways to test are to use the profiler, or
run the app over thousands of actions and see if you eventually reach a
Thanks for the great advice so far...so what is the best way of
freeing Images for gc()? I have a DataGrid that has an itemRenderer
with a mx:Image/...if I have a dataProvider ArrayCollection (where
each records has a URL that the Image uses)...does simply setting the
dataProvider to null take
6 matches
Mail list logo
