Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of maurice.amsellem@systar.com
 designates 216.134.213.70 as permitted sender)
From: Maurice Amsellem <maurice.amsellem@systar.com>
To: "users@flex.apache.org" <users@flex.apache.org>
Subject: RE: Sorting out Memory issues
Thread-Topic: Sorting out Memory issues
Thread-Index: AQHOyklvvZdUICoqn0KHfQaFS7mZ/pn3HDtwgAADBzmAAAHAsA==
Date: Wed, 16 Oct 2013 10:31:10 +0000
Message-ID: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F53608C@EXMBX05.netplexity.local>
References: 
 <3B222F2E298C7C45ACC98C05DCA6BECD4A1E5AC58A@ECCR13PUBLIC.exchange.local>,<2095F5EBE04D59409DFCE91FFCEBF7AF3F536042@EXMBX05.netplexity.local>
 <3B222F2E298C7C45ACC98C05DCA6BECD4A1EDAB5D5@ECCR13PUBLIC.exchange.local>
In-Reply-To: 
 <3B222F2E298C7C45ACC98C05DCA6BECD4A1EDAB5D5@ECCR13PUBLIC.exchange.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Flexicious DataGrid is also excellent :-)

-----Message d'origine-----
De=A0: christofer.dutz@c-ware.de [mailto:christofer.dutz@c-ware.de]=20
Envoy=E9=A0: mercredi 16 octobre 2013 12:25
=C0=A0: users@flex.apache.org
Objet=A0: 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.

Chris

________________________________________
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 Li=
st, 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)=
.

Maurice

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

Hi,

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 a=
nd/or Adobe Versions) I am loading a list of objects and this list is updat=
ed via server-push (Streaming AMF Connection). For testing, I increased the=
 amount of data sent back to the Client when loading the list. Currently ab=
out 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 dat=
a 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 prob=
lems, 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.

Chris