Are you referring to the following bug? http://bugs.adobe.com/jira/browse/FLEXDMV-1968 I think this is fixed in the latest release 3.0.2 not sure.
--- In [email protected], Alex Harui <aha...@...> wrote: > > If you have more header renderers than columns, I'd be checking them for > leaks using the Profiler. > > See http://blogs.adobe.com/aharui/2008/09/using_the_flex_builder_3x_prof.html > for tips on using the Profiler. > > From: [email protected] [mailto:[email protected]] On > Behalf Of djbrown_rotonews > Sent: Friday, November 14, 2008 7:23 AM > To: [email protected] > Subject: [flexcoders] Re: Flex Application Memory Footprint > > > I'm seeing the same behavior. DataGrid headerRenderer is a simple > Label with a toolTip, and there's just 15 columns in the grid > itself. Before the data is even populated, I have 75 instances of > the header renderers (5 for each column), and they never get cleaned > up. > > Around 35-40% of my application memory is then tied up in non- > recycled headerRenderers. > > any ideas? > > --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, "Dimitrios Gianninas" > <dimitrios.gianninas@> wrote: > > > > hi, > > > > when you go to a tab for the first time, it gets created along > with all of its components and they will stay in memory so long as > the app exists. If you are using creationPolicy="all" on your > TabNavigator, that is really bad, dont. That means all tabs are > being created and maybe the user will never go to most of them. > > > > Also if you are caching data that you no longer need, set it to > null to let the GC clean it up. > > > > hope that helps. > > > > Dimitrios Gianninas > > RIA Developer Team Lead > > Optimal Payments Inc. > > > > > > ________________________________ > > > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On Behalf Of Nirav Gosalia > > Sent: Thursday, November 06, 2008 10:21 AM > > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > > Cc: mayank.vora@ > > Subject: [flexcoders] Flex Application Memory Footprint > > > > > > > > Hi, > > > > We are developing a CRM application using Flex. > > > > The SWF size is 1.5 MB. The application has around 15 tabs. When > all the tabs are visited once the application shows a memory foot > print of 400 MB in the windows task manager. > > > > I used flex profiler but there is no memory leak. I was wondering > that how flex handles garbage collection because once the tabs are > created they never seem to be releasing any memory. > > > > Also flex profiler shows that my Datagrid header renderer occupies > 40% of the total memory consumed. > > > > Can someone suggest ways of reducing the memory foot print and > show an ideal way of writing a header renderer (we use it for full > database sort). > > > > Regards, > > > > Nirav Gosalia > > > > > > > > -- > > WARNING > > ------- > > This electronic message and its attachments may contain > confidential, proprietary or legally privileged information, which > is solely for the use of the intended recipient. No privilege or > other rights are waived by any unintended transmission or > unauthorized retransmission of this message. If you are not the > intended recipient of this message, or if you have received it in > error, you should immediately stop reading this message and delete > it and all attachments from your system. The reading, distribution, > copying or other use of this message or its attachments by > unintended recipients is unauthorized and may be unlawful. If you > have received this e-mail in error, please notify the sender. > > > > AVIS IMPORTANT > > -------------- > > Ce message électronique et ses pièces jointes peuvent contenir des > renseignements confidentiels, exclusifs ou légalement privilégiés > destinés au seul usage du destinataire visé. L'expéditeur original > ne renonce à aucun privilège ou à aucun autre droit si le présent > message a été transmis involontairement ou s'il est retransmis sans > son autorisation. Si vous n'êtes pas le destinataire visé du > présent message ou si vous l'avez reçu par erreur, veuillez cesser > immédiatement de le lire et le supprimer, ainsi que toutes ses > pièces jointes, de votre système. La lecture, la distribution, la > copie ou tout autre usage du présent message ou de ses pièces > jointes par des personnes autres que le destinataire visé ne sont > pas autorisés et pourraient être illégaux. Si vous avez reçu ce > courrier électronique par erreur, veuillez en aviser l'expéditeur. > > >
