Yes here: https://bugs.adobe.com/jira/browse/SDK-13549 Also i noticed since the report it was happening not only in Air, but i can't change the post title.
--- In [email protected], "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Florian, > > > > Have you filed a bug for your List scenario with a simple test case? We > want to verify these issues before we ship. > > > > ________________________________ > > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of florian d'erfurth > Sent: Thursday, December 06, 2007 1:45 AM > To: [email protected] > Subject: [flexcomponents] Re: TileList Memory Issues - not freeing up > renderers > > > > 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 [email protected] > <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 > > >
