Sent: Friday, March 03, 2017 2:35 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
On 3/3/17, 1:23 PM, "Jason Taylor" wrote:
>sounds good, this is all stemming from a memory I discovered in our
>SparkTree component which is based off
>https://github.com
On 3/3/17, 1:23 PM, "Jason Taylor" wrote:
>sounds good, this is all stemming from a memory I discovered in our
>SparkTree component which is based off
>https://github.com/kachurovskiy/Spark-Tree which I'm sure a lot of people
>use. In the middle of redesigning a solid tree component based of
>
performant with a lot less
code complexity, and hopefully dosen't exhibit the memory leak issue.
~ JT
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Friday, March 03, 2017 11:26 AM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
What I someti
ch 02, 2017 8:45 PM
>To: dev@flex.apache.org
>Subject: Re: massive memory leak in Flex
>
>So what OS and version, and what kind of player and its version are you
>using?
>
>Scout will turn on sampling in the app so that should result in an
>increase in memory as well.
&
ence in scout? as I only
>show this leak atm when scout is ran- Scout 1.1.3.345121 on Scout
>
>-Original Message-
>From: Jason Taylor
>Sent: Thursday, March 02, 2017 4:48 PM
>To: dev@flex.apache.org
>Subject: RE: massive memory leak in Flex
>
>what the hell? M
ut? as I only show
>this leak atm when scout is ran- Scout 1.1.3.345121 on Scout
>
>-Original Message-
>From: Jason Taylor
>Sent: Thursday, March 02, 2017 4:48 PM
>To: dev@flex.apache.org
>Subject: RE: massive memory leak in Flex
>
>what the hell? Mine looks
wonder if that might be osx / windows difference in scout? as I only show this
leak atm when scout is ran- Scout 1.1.3.345121 on Scout
-Original Message-
From: Jason Taylor
Sent: Thursday, March 02, 2017 4:48 PM
To: dev@flex.apache.org
Subject: RE: massive memory leak in Flex
what the
what the hell? Mine looks nothing like that in scout, no advanced telemetry
-Original Message-
From: Clint M [mailto:cmod...@gmail.com]
Sent: Thursday, March 02, 2017 4:38 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
it didn't leak using advanced-tele
M [mailto:cmod...@gmail.com]
>> Sent: Thursday, March 02, 2017 4:24 PM
>> To: dev@flex.apache.org
>> Subject: Re: massive memory leak in Flex
>>
>> Can't repro with the code in the original post… here's a video of it
>> running for 60 seconds.
>>
&
---
> From: Clint M [mailto:cmod...@gmail.com]
> Sent: Thursday, March 02, 2017 4:24 PM
> To: dev@flex.apache.org
> Subject: Re: massive memory leak in Flex
>
> Can't repro with the code in the original post… here's a video of it
> running for 60 seconds.
>
> http:/
Yeah, it looks like it may be an artifact of scout somehow
-Original Message-
From: Clint M [mailto:cmod...@gmail.com]
Sent: Thursday, March 02, 2017 4:24 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
Can't repro with the code in the original post… her
Alex Harui [mailto:aha...@adobe.com]
> Sent: Thursday, March 02, 2017 4:07 PM
> To: dev@flex.apache.org
> Subject: Re: massive memory leak in Flex
>
> Scout only reports certain player memory zones. Hopefully TaskManager has
> a higher number? If you got past 1GB then it probably isn
Yeap task manager keeps climbing as well
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Thursday, March 02, 2017 4:07 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
Scout only reports certain player memory zones. Hopefully TaskManager has a
it happens without specificy a itemrenderer as well
-Original Message-
From: Clint M [mailto:cmod...@gmail.com]
Sent: Thursday, March 02, 2017 4:07 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
databinding is static at the application level… at least the way you&#x
";
> xmlns:s="library://ns.adobe.com/flex/spark" creationComplete="
> OnCreationComplete(event)">
>
>
>
>
>
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Thursday, March 02, 2017 3:47 PM
> T
gt;-Original Message-
>From: Alex Harui [mailto:aha...@adobe.com]
>Sent: Thursday, March 02, 2017 3:54 PM
>To: dev@flex.apache.org
>Subject: Re: massive memory leak in Flex
>
>OK Thanks. Sounds like Justin may be digging into it, so I'll wait until
>he reports in. Whi
Tried 4.13, 14, and 15, but I have a weird feeling scout is a dirty Liar
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Thursday, March 02, 2017 3:54 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
OK Thanks. Sounds like Justin may be digging
3:50 PM
To: dev@flex.apache.org
Subject: RE: massive memory leak in Flex
This is all the code needed to cause it, and no it does not appear to stop,
though I will need to run it for awhile to blow all my memory in this comp.
http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.
t;
>
>
>
>-Original Message-
>From: Alex Harui [mailto:aha...@adobe.com]
>Sent: Thursday, March 02, 2017 3:47 PM
>To: dev@flex.apache.org
>Subject: Re: massive memory leak in Flex
>
>Jason, we aren't seeing all of the code. Can you put all of the code in
>
eationComplete(event)">
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Thursday, March 02, 2017 3:47 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
Jason, we aren't seeing all of the code. Can you put all of the code in a JIRA
issue?
T
py 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
>Subjec
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
Hi,
What's the code for your TestItemRenderer? If you remove that does it act the
same?
Thanks,
Justin
climbing at 50Mb per 30s
-Original Message-
From: Jason Taylor [mailto:ja...@dedoose.com]
Sent: Thursday, March 02, 2017 3:32 PM
To: dev@flex.apache.org
Subject: RE: massive memory leak in Flex
negative, taking that out (that was an accident copied over from my real test),
has no
eationComplete(event)">
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Thursday, March 02, 2017 3:00 PM
To: dev@flex.apache.org
Subject: Re: massive memory leak in Flex
On 3/2/17, 2:56 PM, "Justin Mclean" wrote:
>Hi,
>
>Also I’d suggest making the time
On 3/2/17, 2:56 PM, "Justin Mclean" wrote:
>Hi,
>
>Also I’d suggest making the timer multi shot rather than having the
>recursive callLater(BindData) call.
IMO, that's the root of the problem. The timer makes calls to BindData
which also calls itself on each frame via CallLater. Each Timer t
Hi,
Also I’d suggest making the timer multi shot rather than having the recursive
callLater(BindData) call.
Thanks,
Justin
Hi,
If you put:
list.dataProvider = null;
before the line;
list.dataProvider = new ArrayCollection(items);
Do you getter same results?
Thanks,
Justin
Also here's a screen shot of Scout - http://imgur.com/a/WCkZu
-Original Message-
From: Jason Taylor [mailto:ja...@dedoose.com]
Sent: Thursday, March 02, 2017 2:37 PM
To: dev@flex.apache.org
Subject: massive memory leak in Flex
I believe I have finally identified the cause of a
I believe I have finally identified the cause of a huge memory leak in our
application, and it appears to be s:label
I have tested this on many different framework versions.
Please try the following:if you make a custom itemrender and don't use the
s:label it goes away, note disabiling TextL
30 matches
Mail list logo
