player 22, windows 7 64, when scout is running it appears no objects get released to the gc, so this appears to be a bug with scout.
-----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, March 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. -Alex On 3/2/17, 4:48 PM, "Jason Taylor" <ja...@dedoose.com> wrote: >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 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-telemetry either… it didn't leak with a >custom renderer with curly binding either… probably because spark lists >recycle item renderers by default > >On Thu, Mar 2, 2017 at 4:29 PM, Clint M <cmod...@gmail.com> wrote: > >> here's a video of it running in scout >> http://www.screencast.com/t/S5SHGLiskRN >> >> didn't leak… are you using advanced-telemetry ? >> >> On Thu, Mar 2, 2017 at 4:24 PM, Jason Taylor <ja...@dedoose.com> wrote: >> >>> 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… here's a video of it >>> running for 60 seconds. >>> >>> http://www.screencast.com/t/mPFMIdKQMK >>> >>> On Thu, Mar 2, 2017 at 4:17 PM, Jason Taylor <ja...@dedoose.com> wrote: >>> >>> > 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 higher number? If you got past 1GB then it >>>probably isn't capped. >>> > >>> > -Alex >>> > >>> > On 3/2/17, 3:56 PM, "Jason Taylor" <ja...@dedoose.com> wrote: >>> > >>> > >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 into it, so I'll >>> > >wait until he reports in. Which version of Apache Flex are you >>>using? >>> > >Have you tried Adobe Flex 4.6? >>> > > >>> > >-Alex >>> > > >>> > >On 3/2/17, 3:50 PM, "Jason Taylor" <ja...@dedoose.com> wrote: >>> > > >>> > >>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. >>> > >> >>> > >> >>> > >><?xml version="1.0"?> >>> > >><s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"; >>> > >>xmlns:s="library://ns.adobe.com/flex/spark" >>> > >>creationComplete="OnCreationComplete(event)"> >>> > >> <s:List width="100%" height="100%" id="list"/> >>> > >> <fx:Script><![CDATA[ >>> > >> import mx.collections.ArrayCollection; >>> > >> import mx.events.FlexEvent; >>> > >> >>> > >> private var _bindTimer:Timer; >>> > >> >>> > >> private function OnCreationComplete(event:FlexEvent):void >>> > >> { >>> > >> _bindTimer = new Timer(500); >>> > >> _bindTimer.addEventListener(TimerEvent.TIMER, >>> > >>OnBindTimerTick, false, 0, true); >>> > >> _bindTimer.start(); >>> > >> } >>> > >> >>> > >> private function OnBindTimerTick(event:TimerEvent):void >>> > >> { >>> > >> BindData(); >>> > >> } >>> > >> >>> > >> private function BindData():void >>> > >> { >>> > >> var items:Array = []; >>> > >> for (var i:uint = 0; i < 100; i++) >>> > >> { >>> > >> items.push(GenerateRandomString(100)); >>> > >> } >>> > >> list.dataProvider = null; >>> > >> list.dataProvider = new ArrayCollection(items); >>> > >> } >>> > >> >>> > >> private function GenerateRandomString(strlen:Number):String >>> > >> { >>> > >> var chars:String = >>> > >>"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"; >>> > >> var num_chars:Number = chars.length - 1; >>> > >> var randomChar:String = ""; >>> > >> >>> > >> for (var i:Number = 0; i < strlen; i++) >>> > >> { >>> > >> randomChar += >>> > >>chars.charAt(Math.floor(Math.random() >>> > >>* num_chars)); >>> > >> } >>> > >> return randomChar; >>> > >> } >>> > >> ]]></fx:Script> >>> > >></s:Application> >>> > >> >>> > >> >>> > >> >>> > >>-----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? >>> > >> >>> > >>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 >>> > >> >>> > > >>> > >>> > >>> >> >>
