On Feb 23, 2016 19:34, "Alex Harui" wrote:
> OK, so I'll get the compiler to map Date's properties to getX/setX calls.
>
> For Array.sort, I guess we should map it to some other function in some
> other class. Should we generalize such a mapping or is that the only one?
>
> -Alex
>
>
These cons
Go for it!
On 2/24/16, 1:50 PM, "Christofer Dutz" wrote:
>I think removing this should be as easy as deleting the 3 other
>messages_xx.properties files. The code seems to look for a resource
>bundle in the current language and if that fails, it falls back to
>english. So deleting these files sho
I think removing this should be as easy as deleting the 3 other
messages_xx.properties files. The code seems to look for a resource bundle in
the current language and if that fails, it falls back to english. So deleting
these files should resolve these issues and it would eliminate the danger I
On 2/24/16, 10:13 AM, "Clint M" wrote:
>I was able to reproduce the behavior while using the references array and
>uncommenting the line:
>
>references.splice( references.indexOf(lastInstance),1);
>
>It might be that Player holds a reference to the object spliced out
>because
>it does return it
I was able to reproduce the behavior while using the references array and
uncommenting the line:
references.splice( references.indexOf(lastInstance),1);
It might be that Player holds a reference to the object spliced out because
it does return it.
In any case... I'd like to reiterate that it doe
I removed the references array, slowed the timer down to 1 second and
found that if I hit the GC button in the profiler, the instance count goes
back to 1 or 2, which is correct, so NonLeakySubComponent is not leaking,
without having to delete layoutObject. Make sure you are looking at
instance co
Wow, that's really interesting. I'd be happy to simplify and remove
localized compiler errors. I suppose an alternative is to add an error
"identifier" to the error output. I think an error number is currently
used, but error numbers don't really help in a search. I think other
compilers use be
I took a quick look at the test case (I haven't even tried it in the
profiler yet).
I assume the test case to run is LeakByReference.mxml. In the run()
method, it keeps storing references to the new NonLeakySubComponent on
every pass, so sure, if you don't splice out the references to the old
one
In the past, I have heard other non-English speakers say the same thing as
Chris and Félix. There's more web content (blog posts, forum threads, etc.)
about the English error messages, so trying to search for the error in
other languages ends up excluding relevant content.
- Josh
On Wed, Feb 24,
Hello,
On Wed, Feb 24, 2016 at 5:56 PM, Christofer Dutz
wrote:
> Actually in the past they have slowed me down, cause if I have an error,
> which I don't understand, I can be certain that I need to feed google with
> the english version, so I tried to guess the english one and eventually
> look
Actually in the past they have slowed me down, cause if I have an error, which
I don't understand, I can be certain that I need to feed google with the
english version, so I tried to guess the english one and eventually look it up
in the resource-bundles :-)
Chris
_
Hi Clint,
Flash Profiler has a functionality to force garbage collection. I press the
button several times and there's no instance being freed. Besides, taking a
memory snapshot also forces garbage collection.
On the other hand, after several hours of Flash Profiling, I have found a
workaround by
On 2/24/16, 8:18 AM, "Christofer Dutz" wrote:
>Well if we leave them in there, I would suggest to write a test, that
>assures all versions have the same properties. If a new one is added to
>the english or removed it should fail with a message. This way I think we
>should be able to maintain th
On 2/24/16, 8:15 AM, "Christofer Dutz" wrote:
>Well I am using my mavenized sdks my sdk-converter provides me ... and I
>have all of these resource bundles available.
>
>Anyway ... I just finished releasing a new version of JBurg, that no
>longer has the classloader issues the 1.10.2 version ha
Well... it's not technically leaking... it just appears like it is because
the timer is firing every 10 ms which doesn't let garbage collection run as
fast as you think it should.
It will eventually run... you just have to wait a really long time. (Most
likely when your physical ram is full.)
In
Well if we leave them in there, I would suggest to write a test, that assures
all versions have the same properties. If a new one is added to the english or
removed it should fail with a message. This way I think we should be able to
maintain the resources manually ... I bet we have people here
On 2/24/16, 12:08 AM, "Christofer Dutz" wrote:
>Hi Alex,
>
>that sounds as if you are using assertions in a way that contradictory to
>what they are intended to be used.
It isn't me. I did not write this code or review it. Before Flex moved
to Apache, I had made maybe a half-dozen changes to
Well I am using my mavenized sdks my sdk-converter provides me ... and I have
all of these resource bundles available.
Anyway ... I just finished releasing a new version of JBurg, that no longer has
the classloader issues the 1.10.2 version had (JBurg 1.10.2 used the system
classloader to load
On 2/24/16, 4:19 AM, "Christofer Dutz" wrote:
>Hi,
>
>so I managed to get all Unit-Tests to pass:
>"Tests run: 375, Failures: 0, Errors: 0, Skipped: 26"
Yay!
>currently having a little trouble with the resource-bundles as I'm
>getting a lot of:
>"Error: Unable to resolve resource bundle 'mess
On 2/24/16, 3:26 AM, "Christofer Dutz" wrote:
>Ok ... now this is strange. I found out that my resource bundle generator
>needed a small change.
>The original appended the messages to the messages_en.properties. So the
>generated output is automatically appended to the stuff checked in in the
>
Great work! Thanks for doing this!!!
Harbs
On Feb 24, 2016, at 2:19 PM, Christofer Dutz wrote:
> Hi,
>
> so I managed to get all Unit-Tests to pass:
> "Tests run: 375, Failures: 0, Errors: 0, Skipped: 26"
>
> And most of the integration-tests running:
> "Tests run: 124, Failures: 32, Errors:
Hi,
so I managed to get all Unit-Tests to pass:
"Tests run: 375, Failures: 0, Errors: 0, Skipped: 26"
And most of the integration-tests running:
"Tests run: 124, Failures: 32, Errors: 0, Skipped: 5"
currently having a little trouble with the resource-bundles as I'm getting a
lot of:
"Error: Una
Ok ... now this is strange. I found out that my resource bundle generator
needed a small change.
The original appended the messages to the messages_en.properties. So the
generated output is automatically appended to the stuff checked in in the
messages_en.properties from the src/main/resources d
Oh gee .. forget what I just wrote ... it's already done that way :-(
Chris
Von: Christofer Dutz
Gesendet: Mittwoch, 24. Februar 2016 11:25
An: 'dev@flex.apache.org'
Betreff: Think I found out, why the falcon integration-tests never succeed when
running
Hi,
while trying to make the unit-tests run with maven I stumbled over something. I
got some crazy errors when running some tests. While tracing them down, I could
see that the "problem output" fails cause no format is specified. This is
because a NullPointerException occurs in the compiler ..
Hi all,
Ok ... so as the Ant build seems to have assertions disabled, I disabled them
for the Maven build as well:
Tests run: 375, Failures: 0, Errors: 0, Skipped: 26
But we should fix this as soon as possible.
Also I added my changes with the TestAdapters to the develop branch. It
shouldn't
Thanks Clint, but I've commented it as well and the memory leak is still
happening. Profiler still reports memory constantly increasing. I've also
commented the other addEventListener calls just in case, and the only way to
stop the leak is by commenting on addEventListener(). Did the Flash Profile
Hi Alex,
that sounds as if you are using assertions in a way that contradictory to what
they are intended to be used.
Assertions are meant to be hard checks to the contract of a method. Assumptions
the code needs to operate correctly.
Usually you could do the same with if-statements, but in con
28 matches
Mail list logo
