I reported on a bug similar to this in Sept (SDK-12824) and it has been deferred. My hack fix was to explicitly include the TileBase etc classes into my project and then make the calls to addToFreeItemRenderer in the appropriate places the renderers are now reused and both performance and memory usage improved. Would be nice if this was fixed.
-scott On 12/6/07 12:16 PM, "ven" <[EMAIL PROTECTED]> wrote: > > > > > I logged the issue with a screenshot and a working example. I realized this > issue happens only in AIR application and not in a flex application. I am > using tilelist in an AIR application. > > Bug Key: FLEXDMV-1478 > > ----- Original Message ---- > From: Alex Harui <[EMAIL PROTECTED]> > To: [email protected] > Sent: Thursday, 6 December, 2007 8:58:57 AM > Subject: RE: [flexcomponents] Re: TileList Memory Issues - not freeing up > renderers > > > > > I would need to actually run the code. Please submit a bug with a running test > case, and send me the bug #. > > > > > From: flexcomponents@ yahoogroups. com [mailto:flexcompone [EMAIL PROTECTED] > com] On Behalf Of ven > Sent: Thursday, December 06, 2007 8:50 AM > To: flexcomponents@ yahoogroups. com > Subject: Re: [flexcomponents] Re: TileList Memory Issues - not freeing up > renderers > > > > This is how I am using the TileList and the related classes. Please help me > with this weird problem > > Declaration inside mxml. > > <local:ImageGrid > id="imageGrid" > left="10" right="10" top="10" bottom="10" > backgroundAlpha= "0" borderStyle= "none" > dataChangeEffect= "{imageMoveEffec t}" > dataProvider= "{_dataProvider} " > itemRenderer= "ImageGridRender er" > showEffect=" {imageGridEffect }" > /> > > ImageGrid.mxml > > <mx:TileList > xmlns:mx="http://www.adobe. com/2006/ mxml <http://www.adobe.com/2006/mxml> > " > width="400" height="300" > dragEnabled= "true" > dropEnabled= "true" > dragMoveEnabled= "true" > borderStyle= "none" > borderThickness= "0" > focusThickness= "0" > columnWidth= "110" > rowHeight="120" > /> > > > ImageGridRenderer. mxml > > <mx:VBox > xmlns:mx="http://www.adobe. com/2006/ mxml <http://www.adobe.com/2006/mxml> > " > xmlns:local= "*" > verticalScrollPolic y="off" horizontalScrollPol icy="off" > vert! icalGap= "0" > paddingBottom= "5" paddingLeft= "5" paddingRight= "5" paddingTop=" 5" > verticalAlign= "top" >> > > <local:PreviewBox > id="preview" > width="100%" height="100% " > infoM="{MyInfo( data)}" > imageAlign=" top" > filters="{[new DropShadowFilter( 4, 45, 0, 1)]}" > horizontalScrollPol icy="off" > verticalScrollPolic y="off" > /> > <mx:Canvas width="100%" horizontalScrollPol icy="off"> > <mx:Label > text="{data. name}" > textAlign="center" > width="100%" > selectable=" false" > toolTip="{data. name}" > bottom="0" > /> > </mx:Canvas> > </mx:VBox> > > PreviewBox.as > > <?xml version="1.0" encoding="utf- 8"?> > <mx:Box > xmlns:mx="http://www.adobe. com/2006/ mxml <http://www.adobe.com/2006/mxml> > " > xmlns:local= "*" > borderStyle= "none" > disabledColor= "#888888" > backgroundAlpha= "0" > verticalScrollPolic y="off" > horizontalScrollPol icy="off" >> > > > omitted the script tag for simplicity case. > This class either sets the source for the image as a URL or fetches bitmapdata > and attaches it to the image. It sets the image source to a predefined > bitmapasset until it fetches the actual image data > > <mx:Glow > id="outEffect" duration="300" > alphaFrom="1. 0" alphaTo="0.3" > blurXFrom="15. 0" blurXTo="0" > blurYFrom="15.0" blurYTo="0" > color="0xFFFFFF" > /> > <mx:Glow > id="overEffect" duration="300" > alphaFrom="0. 3" alphaTo="1.0" > blurXFrom="0" blurXTo="15. 0" > blurYFrom="0" blurYTo="15. 0" > color="0xFFFFFF" > /> > <mx:Fade id="showEffect" target="{previewIma ge}" duration="300" > alphaFrom="0" alphaTo="1" /> > > <mx:Canvas width="100%" height="100% " buttonMode=" true" useHandCursor= > "true"> > <mx:Image > id="previewImage" > width="100%" height="100% " > visible="false" > maintainAspectRatio ="true" > horizontalAlign= "center" > verticalCenter= "0"! > horizontalCenter= "0" > verticalAlign= "{imageAlign} " > showEffect=" {showEffect} " > /> > <mx:Button > id="previewBtn" > width="50" height="50" > verticalCenter= "0" horizontalCenter= "0" > visible="{enablePre view(_title) && previewImage. visible}" > includeInLayout= "{showExtras} " > buttonMode=" true" useHandCursor= "true" > upSkin="{InitialPla yButton}" > overSkin="{InitialP layButton} " > downSkin="{InitialP layButtonOver} " > disabledSkin= "{InitialPla! yBut ton}" > click="showPreview( event)" > /> > <local:Spinner > id="bufferingSpinne r" > horizontalCenter= "0" > verticalCenter= "0" > visible="false" > includeInLayout= "{showExtras} " > alpha=".5" > hide="bufferingSpin ner.stop( )" > show="bufferingSpin ner.play( )" > /> > </mx:Canvas> > </mx:Box> > > > > ----- Original Message ---- > From: ben.clinkinbeard <ben.clinkinbeard@ gmail.com> > To: flexcomponents@ yahoogroups. com > Sent: Thursday, 6 December, 2007 7:48:31 AM > Subject: [flexcomponents] Re: TileList Memory Issues - not freeing up > renderers > > Just FYI, its going to be hard for anyone to help either of you unless > you post a test case. > > Ben > > --- In flexcomponents@ yahoogroups. com > <mailto:flexcomponents%40yahoogroups.com> , "florian d'erfurth" > <captain.herisson@ ...> wrote: >> > >> > I don't have any solution but i want to say that it's also happening >> > with List, and not only on scrolling but also on mouse over etc. >> > >> > The bug is only more visible with custom item renderers because they >> > use more memory, anyway seems that's a serious flex bug. >> > >> > --- In flexcomponents@ yahoogroups. com >> <mailto:flexcomponents%40yahoogroups.com> , "rueter007" <rueter007@> wrote: >>> > > >>> > > Hello, I hope Alex or Ted or somebody can be help me with this issue. >>> > > >>> > > I am using a Tilelist component with custom item renderers(image and >>> > > some text). I knew that the list and grid components reuse the item >>> > > renderers rather than creating new ones. But the tilelist is behaving >>> > > weirdly. Everytime I scroll down through the TileList, it is creating >>> > > new renderers and not freeing up the old ones. When I scroll back up, >>> > > it is creating new renderers again. The same happens when the >>> > > dataprovider changes. So, the memory quickly jumps very high even upon >>> > > simple scrolling and the application crashes. These renderers are >>> > > never let go. So if I have 10 items in the tilelist and I scroll up >>> > > and down a few times, the number of renderers goes to 200 or even >>> > > more. I get this information from the profiler. >>> > > >>> > > I do not know what the solution to this problem is. I have searched >>> > > online and saw a couple of other folks have the same issue with the >>> > > tilelist but haven't found a solution. >>> > > >>> > > Any help is appreciated. >>> > > >>> > > thanks, >>> > > venkat >>> > > >> > > > > > > > > Sent from Yahoo! > <http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http:/us.rd.yahoo.com/evt > =51949/*http:/uk.docs.yahoo.com/mail/winter07.html> - the World's favourite > mail. > > > > > > > > Sent from Yahoo! > <http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/ev > t=51949/*http://uk.docs.yahoo.com/mail/winter07.html> - the World's favourite > mail. > >
