Re: [FlexJS] Error with Alert.show
Quick update here, for anyone who may come across this thread: the
Reflection data bug mentioned earlier in the thread is fixed in recent
builds.
On Sat, Feb 18, 2017 at 8:50 PM, Alex Harui wrote:
>
>
> On 2/17/17, 7:50 PM, "Justin Mclean" wrote:
>
> >Hi,
> >
> >Currently when using Alert we’re getting this when compiling:
> >
> >SEVERE: .../javascript/bin/js-debug/org/apache/flex/html/Alert.js:254:
> >ERROR - Object literal contains illegal duplicate key "show", disallowed
> >in ES5 strict mode
> >'show': { type: 'void', declaredBy: 'org.apache.flex.html.Alert',
> >parameters: function () { return [ { index: 1, type: 'Object', optional:
> >false } ]; }}
> >^^
>
> That's a bug in the Reflection data. For I worked around it in
> SimpleAlert by renaming show to showAlert so the static show calls
> showAlert. Looks like I should have applied the same hack to Alert. So
> maybe try that same change to get past this error.
>
> HTH,
> -Alex
>
>
Re: [FlexJS] Any gude to getting checkintests working
On 3/2/17, 10:25 PM, "Greg Dove" wrote: >I must have missed that discussion! That also helps! >I'm getting closer, now have local trust/security sandbox issues for the >flex-sdk tests that I will need to resolve. Oh yeah, I generally open a folder containing my repos to Flash. See http://help.adobe.com/en_US/FlashPlayer/LSM/WS6aa5ec234ff3f285139dc56112e37 86b68c-7fea.html To access those settings, run one of our FlexJS SWF examples or any Flash content then right-click. Thanks, -Alex
Re: [FlexJS] Any gude to getting checkintests working
I must have missed that discussion! That also helps! I'm getting closer, now have local trust/security sandbox issues for the flex-sdk tests that I will need to resolve. I will circle back to that tomorrow morning. If I get this working then I assume the as-js version will be straightforward (fingerscrossed). Thanks for stepping me through this, I am sure I will get there tomorrow. On Fri, Mar 3, 2017 at 7:02 PM, Alex Harui wrote: > > > On 3/2/17, 9:56 PM, "Greg Dove" wrote: > > >Thanks, that helps, it looks like I can make more progress on this now. > > > >Also, fyi I am getting a download error for > >https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/ > trunk/lib/afe.jar?for > >mat=raw > > > >if I choose the adobe jars in that build. > > That got discussed here: > http://mail-archives.apache.org/mod_mbox/flex-dev/201702. > mbox/%3cD4BE9406.8 > 42df%25aha...@adobe.com%3e > > Thanks, > -Alex > >
Re: [FlexJS] Any gude to getting checkintests working
On 3/2/17, 9:56 PM, "Greg Dove" wrote: >Thanks, that helps, it looks like I can make more progress on this now. > >Also, fyi I am getting a download error for >https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/lib/afe.jar?for >mat=raw > >if I choose the adobe jars in that build. That got discussed here: http://mail-archives.apache.org/mod_mbox/flex-dev/201702.mbox/%3cD4BE9406.8 42df%25aha...@adobe.com%3e Thanks, -Alex
Re: [FlexJS] Any gude to getting checkintests working
Thanks, that helps, it looks like I can make more progress on this now. Also, fyi I am getting a download error for https://sourceforge.net/adobe/flexsdk/code/HEAD/tree/trunk/lib/afe.jar?format=raw if I choose the adobe jars in that build. On Fri, Mar 3, 2017 at 6:37 PM, Alex Harui wrote: > Hi Greg, > > So do you have a flex-sdk repo folder as a sibling of flex-asjs? > And have you run "ant main checkintests" in flex-sdk? That should build a > mustella.swc in the flex-sdk/mustella folder that the flex-asjs > checkintests borrows. UnitTester comes from that swc. > > HTH, > -Alex > > BTW, checkintests doesn't really do much right now, but hopefully it will > someday so it is great that you are taking the time to try to get it to > work. > > > On 3/2/17, 9:14 PM, "Greg Dove" wrote: > > >Thanks Alex, > > > >after running > >ant checkintests > >inside flex-asjs > > > >The first point of fail is at basictests task > > > >basictests: > >[mxmlc] Loading configuration: > >D:\FLEXSDKS\_asf\flex-asjs\frameworks\flex-config.xml > >[mxmlc] Loading configuration: > >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\ > BasicTestsApp-config. > >xml > >[mxmlc] > >[mxmlc] > >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\ > FlexJSContext.as(32): > >col: 3 Error: Access of possibly undefined property UnitTester. > >[mxmlc] > >[mxmlc] UnitTester.contextFunction = contextFunction; > >[mxmlc] ^ > >[mxmlc] > >[mxmlc] > >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\ > FlexJSContext.as(37): > >col: 10 Error: Access of possibly undefined property UnitTester. > > > >etc. > > > >On Fri, Mar 3, 2017 at 6:09 PM, Alex Harui wrote: > > > >> If you are using Ant, it should just work. It does expect that you > >>have a > >> folder with both flex-asjs and flex-sdk in it, and flex-sdk has been > >>built > >> via its "ant main checkintests". > >> > >> Let me know what error you are getting. > >> > >> -Alex > >> > >> On 3/2/17, 8:59 PM, "Greg Dove" wrote: > >> > >> >There are a few things I have not yet gotten working so far, and the > >>ant > >> >checkintests is one of them. > >> > > >> >If I understand correctly I should be running this before any commit? I > >> >tried to make sense of this today, but it is not so easy (for me) > >>because > >> >I am unfamiliar with this stuff. > >> > > >> >As I have never done this so far, is it ok if I just continue to commit > >> >based on the regular ant and maven builds (with their various tests) > >> >completing successfully? Otherwise if I need to get this set up, is > >>there > >> >a guide to doing so somewhere that I can follow? > >> > > >> > > >> > > >> > >> > >
Re: [Flex JS] Font weight issues
SimpleCSSStylesImpl is Simple. FontWeight is expecting bold or normal
since that's what Flash supports for free and is less code.
Hopefully someday someone will write AdvancedCSSStylesImpl.
Thanks for pointing it out though,
-Alex
On 3/2/17, 9:45 PM, "Justin Mclean" wrote:
>Hi,
>
>Just a FYI in case this trips anyone else up.
>
>The code in applyStyle in SimpleCSSValuesImpl assumes that most CSS style
>numbers are pixels - this is not be the case.
>
>The code in questions is:
>if (typeof(value) == 'number') {
>if (colorStyles[p])
>value = CSSUtils.attributeFromColor(value);
>else
>value = value.toString() + 'px';
>}
>
>Which for font-weight means you can't use values
>100,200,300,400,500,600,700,800 or 900.
>
>Thanks,
>Justin
>
>
[Flex JS] Font weight issues
Hi,
Just a FYI in case this trips anyone else up.
The code in applyStyle in SimpleCSSValuesImpl assumes that most CSS style
numbers are pixels - this is not be the case.
The code in questions is:
if (typeof(value) == 'number') {
if (colorStyles[p])
value = CSSUtils.attributeFromColor(value);
else
value = value.toString() + 'px';
}
Which for font-weight means you can't use values
100,200,300,400,500,600,700,800 or 900.
Thanks,
Justin
Re: [FlexJS] Any gude to getting checkintests working
Hi Greg, So do you have a flex-sdk repo folder as a sibling of flex-asjs? And have you run "ant main checkintests" in flex-sdk? That should build a mustella.swc in the flex-sdk/mustella folder that the flex-asjs checkintests borrows. UnitTester comes from that swc. HTH, -Alex BTW, checkintests doesn't really do much right now, but hopefully it will someday so it is great that you are taking the time to try to get it to work. On 3/2/17, 9:14 PM, "Greg Dove" wrote: >Thanks Alex, > >after running >ant checkintests >inside flex-asjs > >The first point of fail is at basictests task > >basictests: >[mxmlc] Loading configuration: >D:\FLEXSDKS\_asf\flex-asjs\frameworks\flex-config.xml >[mxmlc] Loading configuration: >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\BasicTestsApp-config. >xml >[mxmlc] >[mxmlc] >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\FlexJSContext.as(32): >col: 3 Error: Access of possibly undefined property UnitTester. >[mxmlc] >[mxmlc] UnitTester.contextFunction = contextFunction; >[mxmlc] ^ >[mxmlc] >[mxmlc] >D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\FlexJSContext.as(37): >col: 10 Error: Access of possibly undefined property UnitTester. > >etc. > >On Fri, Mar 3, 2017 at 6:09 PM, Alex Harui wrote: > >> If you are using Ant, it should just work. It does expect that you >>have a >> folder with both flex-asjs and flex-sdk in it, and flex-sdk has been >>built >> via its "ant main checkintests". >> >> Let me know what error you are getting. >> >> -Alex >> >> On 3/2/17, 8:59 PM, "Greg Dove" wrote: >> >> >There are a few things I have not yet gotten working so far, and the >>ant >> >checkintests is one of them. >> > >> >If I understand correctly I should be running this before any commit? I >> >tried to make sense of this today, but it is not so easy (for me) >>because >> >I am unfamiliar with this stuff. >> > >> >As I have never done this so far, is it ok if I just continue to commit >> >based on the regular ant and maven builds (with their various tests) >> >completing successfully? Otherwise if I need to get this set up, is >>there >> >a guide to doing so somewhere that I can follow? >> > >> > >> > >> >>
Re: [FlexJS] Working to fix a compiler bug - problem with the Problems
Hi Greg,
Thanks for digging into this.
Without having dug into it myself, I would like to suggest returning a
type mismatch error of some sort. IIRC, the DuplicateChildTagProblem is
for the following:
The child tag (js:initialView) is really in there twice.
I believe MXML is supposed to treat more than one child in a child tag as
an array. And thus, the equivalent AS code for:
is:
initialView = [ new MyInitialView, new MyOtherInitialView];
If you code that in AS, you will get an error (I hope), and I think the
compiler should report the same error for this MXML scenario, since
initialView is of type IApplicationView or something like that.
And same for the second scenario:
Is the equivalent of:
var initialView:IApplicationView = new SimpleCSSValuesImpl().
My 2 cents,
-Alex
On 3/2/17, 9:09 PM, "Greg Dove" wrote:
>I have been looking into FLEX-35273 [1].
>
>This is a compiler bug where it is possible to do things that don't make
>sense, like:
>
>
>
>
>
>
>or even this :
>
>
>
>
>
>Neither of the above caused compile time errors.
>
>I have a fix for both the above scenarios.
>
>For the first one, I used MXMLDuplicateChildTagProblem which seems 'close
>enough'
>
>"Child tag '${childTag}' bound to namespace '${childNamespace}' is
>already specified for element '${element}'. It will be ignored.";
>
>This renders as :
>Child tag 'MyInitialView' bound to namespace '*' is already specified for
>element 'js:initialView'. It will be ignored.
>
>^
>
>in the first example above. The text does not feel entirely right, but
>seems close enough. "It will be ignored" sounds more like a warning (as
>opposed to an error/failure), which I think a) it should not be and b) it
>is not.
>
>For the second one, I could not find any relevant 'Problem' class (I may
>have missed one perhaps?) So I just made a new one. I don't really know
>what the rules are here.
>These Problems seem to include an error code so I am unclear what to do
>if I add a new one. i.e. it is not clear what new error code I should
>apply (or even if the error code is important for something).
>For now I just added an arbitrary errorCode = 1999 on
>MXMLBadChildTagPropertyAssignmentProblem.
>
>The new problem renders out to :
>In initializer for 'js:initialView', type
>org.apache.flex.core.SimpleCSSValuesImpl is not assignable to target type
>'org.apache.flex.core.IApplicationView'.
>
>Alex, you may be able to advise here are there any rules I need to
>follow for the CompilerProblem classes (in particular, when adding a new
>class).
>
>Assuming all is well above, I will commit this fix tomorrow. I was also
>trying to see if I could figure out how to get checkintests running, but
>I so far I did not. However the regular build tests are all fine with the
>changes I made for this.
>
>
>1. https://issues.apache.org/jira/browse/FLEX-35273
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
On 3/2/17, 8:51 PM, "piotrz" wrote: >I will try to fight with this. The problem is that in this case I don't >have >any exception in the console. :) Yuk. I think I would next examine the DOM. Compare it against the js-debug version. If DOM objects are missing in js-release, then I would set breakpoints where they are created. HTH, -Alex
Re: [FlexJS] Any gude to getting checkintests working
Thanks Alex, after running ant checkintests inside flex-asjs The first point of fail is at basictests task basictests: [mxmlc] Loading configuration: D:\FLEXSDKS\_asf\flex-asjs\frameworks\flex-config.xml [mxmlc] Loading configuration: D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\BasicTestsApp-config.xml [mxmlc] [mxmlc] D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\FlexJSContext.as(32): col: 3 Error: Access of possibly undefined property UnitTester. [mxmlc] [mxmlc] UnitTester.contextFunction = contextFunction; [mxmlc] ^ [mxmlc] [mxmlc] D:\FLEXSDKS\_asf\flex-asjs\mustella\tests\basicTests\FlexJSContext.as(37): col: 10 Error: Access of possibly undefined property UnitTester. etc. On Fri, Mar 3, 2017 at 6:09 PM, Alex Harui wrote: > If you are using Ant, it should just work. It does expect that you have a > folder with both flex-asjs and flex-sdk in it, and flex-sdk has been built > via its "ant main checkintests". > > Let me know what error you are getting. > > -Alex > > On 3/2/17, 8:59 PM, "Greg Dove" wrote: > > >There are a few things I have not yet gotten working so far, and the ant > >checkintests is one of them. > > > >If I understand correctly I should be running this before any commit? I > >tried to make sense of this today, but it is not so easy (for me) because > >I am unfamiliar with this stuff. > > > >As I have never done this so far, is it ok if I just continue to commit > >based on the regular ant and maven builds (with their various tests) > >completing successfully? Otherwise if I need to get this set up, is there > >a guide to doing so somewhere that I can follow? > > > > > > > >
[FlexJS] Working to fix a compiler bug - problem with the Problems
I have been looking into FLEX-35273 [1].
This is a compiler bug where it is possible to do things that don't make sense,
like:
or even this :
Neither of the above caused compile time errors.
I have a fix for both the above scenarios.
For the first one, I used MXMLDuplicateChildTagProblem which seems 'close
enough'
"Child tag '${childTag}' bound to namespace '${childNamespace}' is already
specified for element '${element}'. It will be ignored.";
This renders as :
Child tag 'MyInitialView' bound to namespace '*' is already specified for
element 'js:initialView'. It will be ignored.
^
in the first example above. The text does not feel entirely right, but seems
close enough. "It will be ignored" sounds more like a warning (as opposed to an
error/failure), which I think a) it should not be and b) it is not.
For the second one, I could not find any relevant 'Problem' class (I may have
missed one perhaps?) So I just made a new one. I don't really know what the
rules are here.
These Problems seem to include an error code so I am unclear what to do if I
add a new one. i.e. it is not clear what new error code I should apply (or even
if the error code is important for something).
For now I just added an arbitrary errorCode = 1999 on
MXMLBadChildTagPropertyAssignmentProblem.
The new problem renders out to :
In initializer for 'js:initialView', type
org.apache.flex.core.SimpleCSSValuesImpl is not assignable to target type
'org.apache.flex.core.IApplicationView'.
Alex, you may be able to advise here are there any rules I need to follow
for the CompilerProblem classes (in particular, when adding a new class).
Assuming all is well above, I will commit this fix tomorrow. I was also trying
to see if I could figure out how to get checkintests running, but I so far I
did not. However the regular build tests are all fine with the changes I made
for this.
1. https://issues.apache.org/jira/browse/FLEX-35273
Re: [FlexJS] Any gude to getting checkintests working
If you are using Ant, it should just work. It does expect that you have a folder with both flex-asjs and flex-sdk in it, and flex-sdk has been built via its "ant main checkintests". Let me know what error you are getting. -Alex On 3/2/17, 8:59 PM, "Greg Dove" wrote: >There are a few things I have not yet gotten working so far, and the ant >checkintests is one of them. > >If I understand correctly I should be running this before any commit? I >tried to make sense of this today, but it is not so easy (for me) because >I am unfamiliar with this stuff. > >As I have never done this so far, is it ok if I just continue to commit >based on the regular ant and maven builds (with their various tests) >completing successfully? Otherwise if I need to get this set up, is there >a guide to doing so somewhere that I can follow? > > >
[FlexJS] Any gude to getting checkintests working
There are a few things I have not yet gotten working so far, and the ant checkintests is one of them. If I understand correctly I should be running this before any commit? I tried to make sense of this today, but it is not so easy (for me) because I am unfamiliar with this stuff. As I have never done this so far, is it ok if I just continue to commit based on the regular ant and maven builds (with their various tests) completing successfully? Otherwise if I need to get this set up, is there a guide to doing so somewhere that I can follow?
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
I will try to fight with this. The problem is that in this case I don't have any exception in the console. :) Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p60024.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
On 3/2/17, 5:59 PM, "piotrz" wrote: >Alex, > >What could help you to fix that. Should I try to find in minified JS my >potential class and show it here? I don't know how much time you have, but it would be great if you simply tried to debug into it on your own. Maybe you will find a set of tools and techniques that is better than mine. I think every time, I get an exception in the console, then it is a matter of figuring out what renamed variables map back to the original variable names. For me, I find it difficult to set breakpoints because so many original lines of code have been packed onto a single line. I often delete the source map and hand edit the minified code to break the line of minified code that is throwing the exception into many lines so I can reliably set a breakpoint. Good luck, -Alex
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" 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 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 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 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" 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" 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. >>> > >> >>> > >> >>> > >> >>> > >>http://ns.adobe.com/mxml/2009"; >>> > >>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 >>> > >>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" wrote: >>> > >> >>> > >>>yeah you can remove that, right now mine is just >>> > >>> >>> > >>> >>> > >>>http://ns.adobe.com/mxml/2009"; >>> > >>>xmlns:s="library://ns.adobe.com/flex/spark" >>> > >>>xmlns:Core="CoreClasses.*"> >>> > >>> >>> > >>> >>> > >>> >>> > >>>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 >>> > >> >>> > > >>> > >>> > >>> >> >>
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Alex, What could help you to fix that. Should I try to find in minified JS my potential class and show it here? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p60021.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: massive memory leak in Flex
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 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 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 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" 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" 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. >> > >> >> > >> >> > >> >> > >>http://ns.adobe.com/mxml/2009"; >> > >>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 >> > >>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" wrote: >> > >> >> > >>>yeah you can remove that, right now mine is just >> > >>> >> > >>> >> > >>>http://ns.adobe.com/mxml/2009"; >> > >>>xmlns:s="library://ns.adobe.com/flex/spark" >> > >>>xmlns:Core="CoreClasses.*"> >> > >>> >> > >>> >> > >>> >> > >>>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 >> > >> >> > > >> > >> > >> > >
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 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 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 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" 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" 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. >> > >> >> > >> >> > >> >> > >>http://ns.adobe.com/mxml/2009"; >> > >>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 >> > >>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" wrote: >> > >> >> > >>>yeah you can remove that, right now mine is just >> > >>> >> > >>> >> > >>>http://ns.adobe.com/mxml/2009"; >> > >>>xmlns:s="library://ns.adobe.com/flex/spark" >> > >>>xmlns:Core="CoreClasses.*"> >> > >>> >> > >>> >> > >>> >> > >>>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 >> > >> >> > > >> > >> > >> > >
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 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 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 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" 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" 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. >> > >> >> > >> >> > >> >> > >>http://ns.adobe.com/mxml/2009"; >> > >>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 >> > >>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" wrote: >> > >> >> > >>>yeah you can remove that, right now mine is just >> > >>> >> > >>> >> > >>>http://ns.adobe.com/mxml/2009"; >> > >>>xmlns:s="library://ns.adobe.com/flex/spark" >> > >>>xmlns:Core="CoreClasses.*"> >> > >>> >> > >>> >> > >>> >> > >>>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 >> > >> >> > > >> > >> > >> > >
Re: massive memory leak in Flex
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 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 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" 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" 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. > > >> > > >> > > >> > > >>http://ns.adobe.com/mxml/2009"; > > >>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 > > >>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" wrote: > > >> > > >>>yeah you can remove that, right now mine is just > > >>> > > >>> > > >>>http://ns.adobe.com/mxml/2009"; > > >>>xmlns:s="library://ns.adobe.com/flex/spark" > > >>>xmlns:Core="CoreClasses.*"> > > >>> > > >>> > > >>> > > >>>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 > > >> > > > > > > > >
RE: massive memory leak in Flex
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 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" 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" 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. > >> > >> > >> > >>http://ns.adobe.com/mxml/2009"; > >>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 > >>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" wrote: > >> > >>>yeah you can remove that, right now mine is just > >>> > >>> > >>>http://ns.adobe.com/mxml/2009"; > >>>xmlns:s="library://ns.adobe.com/flex/spark" > >>>xmlns:Core="CoreClasses.*"> > >>> > >>> > >>> > >>>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 > >> > > > >
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 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" 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" 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. > >> > >> > >> > >>http://ns.adobe.com/mxml/2009"; > >>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 > >>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" wrote: > >> > >>>yeah you can remove that, right now mine is just > >>> > >>> > >>>http://ns.adobe.com/mxml/2009"; > >>>xmlns:s="library://ns.adobe.com/flex/spark" > >>>xmlns:Core="CoreClasses.*"> > >>> > >>> > >>> > >>>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 > >> > > > >
RE: massive memory leak in Flex
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" 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" 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. >> >> >> >>http://ns.adobe.com/mxml/2009"; >>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 >>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" wrote: >> >>>yeah you can remove that, right now mine is just >>> >>> >>>http://ns.adobe.com/mxml/2009"; >>>xmlns:s="library://ns.adobe.com/flex/spark" >>>xmlns:Core="CoreClasses.*"> >>> >>> >>> >>>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 >> >
RE: massive memory leak in Flex
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're doing
it via curly braces… and the renderers will leak
try using this in the item renderer instead of text="{data}" and see if that
fixes the problem :
override public function set data(value:Object):void {
mylabelId.text = data
}
On Thu, Mar 2, 2017 at 3:50 PM, Jason Taylor 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.
>
>
>
> http://ns.adobe.com/mxml/2009";
> 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
> 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" wrote:
>
> >yeah you can remove that, right now mine is just
> >
> >
> >http://ns.adobe.com/mxml/2009";
> >xmlns:s="library://ns.adobe.com/flex/spark"
> >xmlns:Core="CoreClasses.*">
> >
> >
> >
> >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
>
>
Re: massive memory leak in Flex
databinding is static at the application level… at least the way you're
doing it via curly braces… and the renderers will leak
try using this in the item renderer instead of text="{data}" and see if
that fixes the problem :
override public function set data(value:Object):void {
mylabelId.text = data
}
On Thu, Mar 2, 2017 at 3:50 PM, Jason Taylor 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.
>
>
>
> http://ns.adobe.com/mxml/2009";
> 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
> 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" wrote:
>
> >yeah you can remove that, right now mine is just
> >
> >
> >http://ns.adobe.com/mxml/2009";
> >xmlns:s="library://ns.adobe.com/flex/spark"
> >xmlns:Core="CoreClasses.*">
> >
> >
> >
> >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
>
>
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" 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" 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. >> >> >> >>http://ns.adobe.com/mxml/2009"; >>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 >>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" wrote: >> >>>yeah you can remove that, right now mine is just >>> >>> >>>http://ns.adobe.com/mxml/2009"; >>>xmlns:s="library://ns.adobe.com/flex/spark" >>>xmlns:Core="CoreClasses.*"> >>> >>> >>> >>>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 >> >
RE: massive memory leak in Flex
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" 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. > > > >http://ns.adobe.com/mxml/2009"; >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 >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" wrote: > >>yeah you can remove that, right now mine is just >> >> >>http://ns.adobe.com/mxml/2009"; >>xmlns:s="library://ns.adobe.com/flex/spark" >>xmlns:Core="CoreClasses.*"> >> >> >> >>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 >
RE: massive memory leak in Flex
Scout is showing 1.5Gb used after 4m, and constantly climbing, however task manager is not reporting the same at all... In scout it showing 1.38GB of that is "Other Bitmap Memory" -Original Message- From: Jason Taylor [mailto:ja...@dedoose.com] Sent: Thursday, March 02, 2017 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.adobe.com/flex/spark" creationComplete="OnCreationComplete(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? 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" wrote: >yeah you can remove that, right now mine is just > > >http://ns.adobe.com/mxml/2009"; >xmlns:s="library://ns.adobe.com/flex/spark" >xmlns:Core="CoreClasses.*"> > > > >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
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" 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. > > > >http://ns.adobe.com/mxml/2009"; >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 >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" wrote: > >>yeah you can remove that, right now mine is just >> >> >>http://ns.adobe.com/mxml/2009"; >>xmlns:s="library://ns.adobe.com/flex/spark" >>xmlns:Core="CoreClasses.*"> >> >> >> >>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 >
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.adobe.com/flex/spark" creationComplete="OnCreationComplete(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? 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" wrote: >yeah you can remove that, right now mine is just > > >http://ns.adobe.com/mxml/2009"; >xmlns:s="library://ns.adobe.com/flex/spark" >xmlns:Core="CoreClasses.*"> > > > >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
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" wrote: >yeah you can remove that, right now mine is just > > >http://ns.adobe.com/mxml/2009"; >xmlns:s="library://ns.adobe.com/flex/spark" >xmlns:Core="CoreClasses.*"> > > > >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
RE: massive memory leak in Flex
yeah you can remove that, right now mine is just http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:Core="CoreClasses.*"> 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
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
RE: massive memory leak in Flex
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 effect, and neither does setting the data provider to null http://ns.adobe.com/mxml/2009"; 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: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 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 tick adds another BindData loop. The call count for BindData should be going up constantly, resulting in flooding memory and GC. But that's just by glancing at the code and screenshot, so I could be wrong. -Alex
RE: massive memory leak in Flex
negative, taking that out (that was an accident copied over from my real test), has no effect, and neither does setting the data provider to null http://ns.adobe.com/mxml/2009"; 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: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 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 tick adds another BindData loop. The call count for BindData should be going up constantly, resulting in flooding memory and GC. But that's just by glancing at the code and screenshot, so I could be wrong. -Alex
Re: massive memory leak in Flex
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 tick adds another BindData loop. The call count for BindData should be going up constantly, resulting in flooding memory and GC. But that's just by glancing at the code and screenshot, so I could be wrong. -Alex
Re: massive memory leak in Flex
Hi, Also I’d suggest making the timer multi shot rather than having the recursive callLater(BindData) call. Thanks, Justin
Re: massive memory leak in Flex
Hi, If you put: list.dataProvider = null; before the line; list.dataProvider = new ArrayCollection(items); Do you getter same results? Thanks, Justin
RE: massive memory leak in Flex
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 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 TextLineReycler has no effect. Using task manager, scout, and IntelliJ Idea Flex profiler all confirm the memory leak. This seems like a massive issue and has been causing a lot of slowdown and crashes in our app. I'm guessing I must have messed something up somewhere as I don't see how sucha massive issue could have been in the framework for soo long (Tested 4.13, 4.14, and 4.15). Please Advise. ~ JT http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" creationComplete="OnCreationComplete(event)">
massive memory leak in Flex
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 TextLineReycler has no effect. Using task manager, scout, and IntelliJ Idea Flex profiler all confirm the memory leak. This seems like a massive issue and has been causing a lot of slowdown and crashes in our app. I'm guessing I must have messed something up somewhere as I don't see how sucha massive issue could have been in the framework for soo long (Tested 4.13, 4.14, and 4.15). Please Advise. ~ JT http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" creationComplete="OnCreationComplete(event)">
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
On 3/2/17, 9:19 AM, "piotrz" wrote: >Alex, > >Do you think because it is something with variable renaming in release >version? >I remember that this problem come back to us. Almost every time js-debug works and js-release doesn't, it has to do with renaming. It is a pain to figure out (at least, I haven't found an easy way), but it is important to find and fix these. -Alex
[4.16.0] # Apache Flex SDK 4.16.0 nightly build 246: Failure
flex-sdk_release-candidate - Build #246 - Failure Changes since last build: No changes For more information, check the console output at http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/246/.
Re: [FlexJS] More event issues
HI, > The problem is that the signature of public function > dispatchEvent(event:Event):Boolean does not work unless flash.events.Event is > specifically specified. I’ve also seen this but it compiles and works fine when I run it. Thanks, Justin
Re: [FlexJS] More event issues
I'm almost at the point where you can try the dual branch, which should in theory take care of this. -Alex On 3/2/17, 2:12 PM, "Harbs" wrote: >I’m struggling with IEventDispatcher. > >I have event proxies which dispatch events from event dispatchers. For >this to work, the pseudo-event dispatcher implements IEventDispatcher, >but does not inherit for EventDispatcher. > >It implements its own dispatchEvent(). The problem is that the signature >of public function dispatchEvent(event:Event):Boolean does not work >unless flash.events.Event is specifically specified. > >Harbs
[FlexJS] More event issues
I’m struggling with IEventDispatcher. I have event proxies which dispatch events from event dispatchers. For this to work, the pseudo-event dispatcher implements IEventDispatcher, but does not inherit for EventDispatcher. It implements its own dispatchEvent(). The problem is that the signature of public function dispatchEvent(event:Event):Boolean does not work unless flash.events.Event is specifically specified. Harbs
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Alex, Do you think because it is something with variable renaming in release version? I remember that this problem come back to us. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59991.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: ArrayElementType?
On 3/2/17, 8:11 AM, "Harbs" wrote: >Interesting. > >So this only works with MXML or with ActionScript too? Just MXML. We could try to get the compiler to use it when checking assignments in ActionScript, but I think that there would be cases where it wouldn't do the right thing since AS allows some forms of automatic type conversion. And still, that would only be compile-time. The Flash runtime does not use Metadata to guide runtime behavior. Vector was introduced to provide runtime support for typed arrays. > >I’m wondering if we can use this for typed arrays in externs compiled >using compc. ExternC will emit ArrayElementType for certain patterns, but not currently for the one you ran into. Thanks, -Alex
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
piotrz wrote > var tmpComp:Button = new Button(true); - need to be true in constructor. I've seen such usage of addition do not works in compiled "bin-release" version. Things not works like 'ripple' etc. in "bin-release" version. Thanks! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59989.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: ArrayElementType?
Interesting.
So this only works with MXML or with ActionScript too?
I’m wondering if we can use this for typed arrays in externs compiled using
compc.
I ran into that problem recently.
> On Mar 2, 2017, at 5:14 PM, Clint M wrote:
>
> It's in the docs:
> http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf680e1-7ffe.html#WS2db454920e96a9e51e63e3d11c0bf69084-7a2c
>
> ArrayElementType metadata tag
>
> When you define an Array variable in ActionScript, you specify Array as the
> data type of the variable. However, you cannot specify the data type of the
> elements of the Array.
>
> To allow the Flex MXML compiler to perform type checking on Array elements,
> you can use the [ArrayElementType] metadata tag to specify the allowed data
> type of the Array elements, as the following example shows:
>
> public class MyTypedArrayComponent extends VBox {
>
>[ArrayElementType("String")]
>public var newStringProperty:Array;
>
>[ArrayElementType("Number")]
>public var newNumberProperty:Array;
>...
> }
> Note: The MXML compiler checks for proper usage of the Array only in MXML
> code; it does not check Array usage in ActionScript code.
> In this example, you specify String as the allowed data type of the Array
> elements. If a user attempts to assign elements of a data type other than
> String to the Array in an MXML file, the compiler issues a syntax error, as
> the following example shows:
>
>
>
>94062
>14850
>53402
>
>
> In this example, you try to use Number objects to initialize the Array, so
> the compiler issues an error.
>
> You can also specify Array properties as tag attributes, rather than using
> child tags, as the following example shows:
>
>
> This MXML code generates an error because Flex cannot convert the Strings
> "abc" and "def" to a Number.
>
> You insert the [ArrayElementType] metadata tag before the variable
> definition. The tag has the following syntax:
>
> [ArrayElementType("elementType")]
> The following table describes the property of the [ArrayElementType]
> metadata tag:
>
> Property
>
> Type
>
> Description
>
> elementType
> String
>
> Specifies the data type of the Array elements, and can be one of the
> ActionScript data types, such as String, Number, class, or interface.
>
> You must specify the type as a fully qualified class name, including the
> package.
>
> On Thu, Mar 2, 2017 at 6:10 AM, Harbs wrote:
>
>> I just noticed a few places in TLF where we have such metadata. For
>> example:
>>
>>[ ArrayElementType("text.elements.TextFlowLine") ]
>>private var _lines:Array;
>>
>> Does anyone know what that does?
>>
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Piotr, Santanu may be right that there are dynamic MXML scenarios involving states and includeIn/excludeFrom. In those cases, the instances are created by MXMLDataInterpreter just like other MXML tags, but may not be added to the DOM until much later, or removed and re-added as states change. I haven't looked at the code, but are you sure that whatever isDynamic does can't be run on addedToParent? Thanks, -Alex On 3/2/17, 5:06 AM, "piotrz" wrote: >Sankar, > >Code which you are showing me should work without the problem. > >var tmpComp:Button = new Button(true); - need to be true in constructor. > >This: > > click="button1_clickHandler(event)" > accent="true"/> > >You don't need any action cause MDL will handle this one. > >Piotr > > > >- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Ch >ild-Problem-tp59595p59983.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: ArrayElementType?
It's in the docs:
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf680e1-7ffe.html#WS2db454920e96a9e51e63e3d11c0bf69084-7a2c
ArrayElementType metadata tag
When you define an Array variable in ActionScript, you specify Array as the
data type of the variable. However, you cannot specify the data type of the
elements of the Array.
To allow the Flex MXML compiler to perform type checking on Array elements,
you can use the [ArrayElementType] metadata tag to specify the allowed data
type of the Array elements, as the following example shows:
public class MyTypedArrayComponent extends VBox {
[ArrayElementType("String")]
public var newStringProperty:Array;
[ArrayElementType("Number")]
public var newNumberProperty:Array;
...
}
Note: The MXML compiler checks for proper usage of the Array only in MXML
code; it does not check Array usage in ActionScript code.
In this example, you specify String as the allowed data type of the Array
elements. If a user attempts to assign elements of a data type other than
String to the Array in an MXML file, the compiler issues a syntax error, as
the following example shows:
94062
14850
53402
In this example, you try to use Number objects to initialize the Array, so
the compiler issues an error.
You can also specify Array properties as tag attributes, rather than using
child tags, as the following example shows:
This MXML code generates an error because Flex cannot convert the Strings
"abc" and "def" to a Number.
You insert the [ArrayElementType] metadata tag before the variable
definition. The tag has the following syntax:
[ArrayElementType("elementType")]
The following table describes the property of the [ArrayElementType]
metadata tag:
Property
Type
Description
elementType
String
Specifies the data type of the Array elements, and can be one of the
ActionScript data types, such as String, Number, class, or interface.
You must specify the type as a fully qualified class name, including the
package.
On Thu, Mar 2, 2017 at 6:10 AM, Harbs wrote:
> I just noticed a few places in TLF where we have such metadata. For
> example:
>
> [ ArrayElementType("text.elements.TextFlowLine") ]
> private var _lines:Array;
>
> Does anyone know what that does?
>
Re: [FlexJS] Coordinate Space
We still have to have FlexJS work on both JS and SWF sides with some compatibility. We could do this: x,y sets "native" values. Reading them back on SWF vs JS might yield different results if padding, border, and margins are set on the parent element. If you don't want your coordinates messed with, then nest your containers and apply padding, border, background, etc to the outer container. And definitely do not use margins. If you want to use CSS to position items, use the top, left, bottom, right style properties (and margin on the children). On the SWF side, these styles will look at the parent's padding and border values and position the elements accordingly (it will use x, y). If you intend to read the values back, they will not necessarily be what you set since the values are determined by the parent's padding and border as well as the child's own margin values. You need to specify layouts inside containers so that the SWF side knows what to do. If you don't intend on using the SWF output, you can just set the style on the container and let HTML/CSS/JS take care of it. If you supply a layout bead, the bead will set the display, positioning, and other styles on the container as necessary and may even impose styles on the children for the JS side. The SWF side is purely programmatic to mimic the JS side and it will be as close as possible but may need to be multiple passes. Scrolling provides more challenges for the SWF side as nested containers need to be used with the outer container used to mask the inner which is then repositioned to simulate scrolling. When you want scrolling, use ScrollableContainer. This class simply sets overflow:auto on the JS side. If you do not want or care about the SWF output, then just set the overflow style on the container. ‹peter On 3/1/17, 4:12 PM, "Justin Mclean" wrote: >Hi, > >> I think we have confusion over what FlexJS is trying to deliver. If we >>are >> trying to make a new Flex that works on both HTML/JS and SWF platforms, >> that, to me, implies SWF is the preferred platform and we need to make >> HTML/JS platform conform to it. Thus the coordinate system needs to >> reflect that. >> >> If we are trying to make it possible to use ActionScript and MXML to >>build >> apps that run on HTML/JS platform primarily with SWF being a good way to >> debug and to also run efficiently, then we need to make clean JS code >>and >> write code to support/mimic that on SWF. > >I not sure home many people are going to use the SWF output, but perhaps >I¹m missing a use case. I expect currently if people are targeting swf, >AIR or mobile they would still use the FlexSDK. Anyone have a different >opionion here? > >The workflow I found to work well as an application developer is >basically to ignore the AS side. Reasons being: >- The framework code is different on the AS side to the JS and has >different features / bugs >- Layout is different between plaftforms and it's a lot of work to get an >application looking the same in both >- AS side is missing support for a number of common style attributes >- Issues setting up debugging support in the IDE >- Chrome has a decent JS debugger now. You can set breakpoints, look at >variables etc etc >- Project I¹m working on is targeting JS as final output > >You still get the benefits of coding in AS and the IDE and compiler pick >up a lot of issues for you quickly because of that. > >> I am not a JavaScript developer so I don't know what JS >> folks come to expect and how they work with this coordinate system. >>Maybe >> most of the UI is static and the apps just use form fields for input and >> effects are set up in CSS and then triggered so programmatic >>manipulation >> of object position is rare; I don't know. > >Programmatic manipulation currently is required (IMO) if you want your >application to resize nicely / be responsive. > >If % x, % y, min width / height and max width / height were implemented >and/or % height and % width worked differently then it may not be so >important. > >Thanks, >Justin
ArrayElementType?
I just noticed a few places in TLF where we have such metadata. For example:
[ ArrayElementType("text.elements.TextFlowLine") ]
private var _lines:Array;
Does anyone know what that does?
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Sankar, Code which you are showing me should work without the problem. var tmpComp:Button = new Button(true); - need to be true in constructor. This: You don't need any action cause MDL will handle this one. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59983.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
piotrz wrote > Ok but you didn't add this Grid to MXML, you will add this component by > addElement yes ? > > Maybe I do not understand your use cases - provide me an example if you > can. Hi Piotr, My test was pretty basic with FlexJS MDL default components only. Here's the basic test case where I added a MDL button to one GridCell after a button click: https://kobra.io/#/e/-KeE-9-OM5UGpVORDPwt Thanks! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59982.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Sankar, Ok but you didn't add this Grid to MXML, you will add this component by addElement yes ? If you are adding Grid in MXML - It will be initialized on his own - MDL will upgrade it automatically. Maybe I do not understand your use cases - provide me an example if you can. If you have created your custom component it is your responsibility to make upgrade, I can only add upgrade to the component which we currently created with Carlos. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59981.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Hi Piotr, I may oppose this your opinion: piotrz wrote > I don't see any advantage to have this property in MXML. Dynamic component > is supposed to be created from code new Button(true). Say I have an external Grid component which has many buttons and TextFields declared in MXML tag - and I wants to add that external Grid component to somewhere at runtime. So in the way your opinion, I see the dynamic addition and component upgrade will going to fail, unless I write every component addition code in that external Grid component in area. Secondly, have you tried your fix in "bin-release" version? I did a small test by adding a button the way constructor demands it; it does well in "bin-debug" version though but "bin-release". Thanks! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59980.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Hi Sankar, I don't see any advantage to have this property in MXML. Dynamic component is supposed to be created from code new Button(true). If you need more dynamic components which is already in our MDL library let me know. I've changed only few of them to be dynamic. If component do not have in the constructor isDynamic you may try to add UpgradeElement bead during creation, but it won't guarantee that your component will be refreshed. Sometimes refreshing required refreshing also sub components. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59979.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MDL Dialogs] was: Re: [FlexJS] MDL - Dynamic Child Problem
Hi, I recently updated my local framework source from Git repository. I am not sure where we're standing now with this but I wanted to give Piotr's Button and TextField implementation a try with new UpgradeElement bead. So far I able to get the dynamic element upgraded by this way: var newButton:Button = new Button(true); Piotr, I have a question: - I didn't seen any "isDynamic" property in MXML declaration as I know the property was only limited to constructor. Are you planning to do something on this? Also, if I have a component filled with many elements, i.e. buttons, textfields etc. and want to add that component at runtime, I shall basically needs to set "isDynamic=true" to every components in it, is that right? Thanks! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59978.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
