Jason, we aren't seeing all of the code.  Can you put all of the code in a
JIRA issue?

There is a notion of outrunning GC.  And also memory fragmentation.  How
high does memory go?  Does it cap out or will it blow up for lack of
memory at some point?

Thanks,
-Alex

On 3/2/17, 3:39 PM, "Jason Taylor" <ja...@dedoose.com> wrote:

>yeah you can remove that, right now mine is just
>
><?xml version="1.0"?>
><s:ItemRenderer xmlns:fx="http://ns.adobe.com/mxml/2009";
>xmlns:s="library://ns.adobe.com/flex/spark"
>                xmlns:Core="CoreClasses.*">
>    <Core:MyLabel width="100%" height="100%" text="{data}"/>
></s:ItemRenderer>
>
>where MyLabel is a copy of s:label so I can make changes and try to
>figure out where the hell this is coming from, appears to be deep in TLF
>
>-----Original Message-----
>From: Justin Mclean [mailto:jus...@classsoftware.com]
>Sent: Thursday, March 02, 2017 3:38 PM
>To: dev@flex.apache.org
>Subject: Re: massive memory leak in Flex
>
>Hi,
>
>What's the code for your TestItemRenderer? If you remove that does it act
>the same?
>
>Thanks,
>Justin

Reply via email to