flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maurice Amsellem <maurice.amsel...@systar.com>
Subject RE: Sorting out Memory issues
Date Wed, 16 Oct 2013 10:31:10 GMT
Flexicious DataGrid is also excellent :-)

-----Message d'origine-----
De : christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de] 
Envoyé : mercredi 16 octobre 2013 12:25
À : users@flex.apache.org
Objet : AW: Sorting out Memory issues

Hi Maurice,

Hmmm ... I think I could try that. Think it would be even easier to comment out the list entirely
in a first step as reloading and storing of data is handled Independent of the displaying
component. So' I'd be loading of data and refreshing of the list and see if everything is
cleaned up correctlry. If that doesn't have the same Memory issues looking as Spark Grids
woud be good.


Von: Maurice Amsellem [maurice.amsellem@systar.com]
Gesendet: Mittwoch, 16. Oktober 2013 12:16
An: users@flex.apache.org
Betreff: RE: Sorting out Memory issues

Can you try doing the same with a spark DataGrid, or even a simple spark List, to see if previous
items are locked by the ArrayList (which I doubt) or by the Flexicious DataGrid (maybe caching,
or adding events, or something).


-----Message d'origine-----
De : christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]
Envoyé : mercredi 16 octobre 2013 10:27
À : users@flex.apache.org
Objet : Sorting out Memory issues


I am currently having Major Memory issues, which I haven't quite managed to sort out.

In my application (Apache Flex 4.10 ... but wasn't any different in older and/or Adobe Versions)
I am loading a list of objects and this list is updated via server-push (Streaming AMF Connection).
For testing, I increased the amount of data sent back to the Client when loading the list.
Currently about 12000 Objects are returned using about 107MB (according to Adobe Scout).

The returned list of objects is displayed in a Flexicious Ultimate DataGrid (The Performance
of this is very sattisfying considering the amount of data it has to handle).

There is a Feature to force a reload of the list. As removing all elements of an ArrayList
and then adding 12000 Objects caused Major Performance problems, I changed the code to replace
the source array of the ArrayCollection and then to make the list update itself after that.
Each time the list is reloaded 107MB are used but I can't see any Memory being freed.

Is there something wrong with my Approach? Do I have to Keep something else in mind? Are there
some hidden internals keeping a reference to my objects so they aren't cleaned up?

Help greatly appreciated.


View raw message