Oh,
ok ... indeed I was talking about the hanging of the build were you have to
kill the process.
Sorry for the confusion.
Chris
Am 22.05.20, 13:18 schrieb "Carlos Rovira" <carlosrov...@apache.org>:
Hi Chris,
maybe we're talking on different issues. The current problem is when
compiling or building a final application, so the compiler behaves
strangely sometimes doing things differently (for that reason I was
pointing to some thread throttle issue). If I understand you right, I think
you're pointing to royale 3 repos building issues that from time to time
can hang. That use to be less frecuent than the problem I raise here.
El jue., 21 may. 2020 a las 8:43, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:
> Hi folks,
>
> I think it might be a resource leak between multiple module compilations.
>
> I never had the issue when running only one module but hat it quite
> regularly when doing the full build with all modules. So I guess probably
> the modules coming later in the build have a higher chance of running into
> this problem.
>
> Things did improve when Greg fixed one of the leaks.
> But it hasn't gone away completely.
>
> Chris
> ________________________________
> Von: Carlos Rovira <carlosrov...@apache.org>
> Gesendet: Mittwoch, 20. Mai 2020 17:48
> An: Apache Royale Development <dev@royale.apache.org>
> Betreff: Re: About the cumbersome random compilation issue
>
> Hi Greg,
>
> next time I'll get a fail compilation I'll store the results and comment.
> Other thing I'm wondering if is something only related to TDJ (jewel apps)
> and that's not happening for Basic, Express, or MXRoyale
>
>
> El mar., 19 may. 2020 a las 0:04, Greg Dove (<greg.d...@gmail.com>)
> escribió:
>
> > Carlos, it would be good to know if the issue you are seeing is the same
> > thing.
> >
> > I know you test mainly in release builds, so if you experience that
issue
> > in a release build, can you confirm the issue is the same as Brian
> reported
> > (missing 'prototype._bindings = [...' in the corresponding debug build?
> >
> >
> >
> >
> > On Tue, May 19, 2020 at 9:55 AM Carlos Rovira <carlosrov...@apache.org>
> > wrote:
> >
> > > Thanks Brian,
> > >
> > > I forgot you already sent similar info some weeks ago.
> > >
> > > @Greg, you that know that code better, maybe there's some thread issue
> > > here? For something that works sometime ok and others not, I think
that
> > > random behaviour seems a thread issue where there's no syncing. Have
> that
> > > sense?
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> > >
> > > El lun., 18 may. 2020 a las 20:17, Greg Dove (<greg.d...@gmail.com>)
> > > escribió:
> > >
> > > > That's interesting Brian, thanks for sharing that.
> > > >
> > > > I have been working on a fix for inherited bindings, which is
> something
> > > > that has never worked but which I needed to work (I now have that
> > working
> > > > locally and expect to get that in today). I am not exactly sure why
> > what
> > > > your saw was happening, but I have made another change locally which
> > > could
> > > > theoretically reduce the possibility of the type of thing you
> described
> > > > from happening. I was going to revert it, as it is not central to
the
> > > issue
> > > > for inherited bindings, but I will do more extensive testing with it
> > > > included and see if it is ok to leave in.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 19, 2020 at 5:35 AM Brian Raymes <
> brian.ray...@teotech.com
> > >
> > > > wrote:
> > > >
> > > > > I cannot speak for js-release, but it happens to me with js-debug
> in
> > > what
> > > > > seems like 1 in every 10 builds. Possibly more often.
> > > > >
> > > > > I've made copies a couple times to compare the output. Each time,
> it
> > > > > appears that some "prototype._bindings" are missing. Here is
> example
> > > > > related to TourDeJewel:
> > > > >
> > > > > In NavigationGroupExampleItemRenderer.js, the following is missing
> > > > > entirely in a bad build:
> > > > >
> > > > > /**
> > > > > * @export
> > > > > */
> > > > >
> itemRenderers.NavigationGroupExampleItemRenderer.prototype._bindings
> > =
> > > [
> > > > > //
> > > > > // contents removed for brevity
> > > > > //
> > > > > ];
> > > > >
> > > > > Several of these "xxxxx.prototype._bindings" sections were missing
> > from
> > > > > the generated JavaScript.
> > > > >
> > > > > Hope this helps.
> > > > >
> > > > > Brian
> > > > >
> > > > > -----Original Message-----
> > > > > From: Alex Harui <aha...@adobe.com.INVALID>
> > > > > Sent: Sunday, May 17, 2020 8:26 AM
> > > > > To: dev@royale.apache.org
> > > > > Subject: Re: About the cumbersome random compilation issue
> > > > >
> > > > > BTW, is this in js-debug or js-release?
> > > > >
> > > > > On 5/17/20, 8:20 AM, "Alex Harui" <aha...@adobe.com.INVALID>
> wrote:
> > > > >
> > > > > Save a good build. When you think you have a bad build,
compare
> > the
> > > > > output.
> > > > >
> > > > > On 5/17/20, 3:46 AM, "Carlos Rovira" <carlosrov...@apache.org>
> > > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I want to open a thread about how to solve the weird
random
> > > > > compilation
> > > > > issue where, from time to time, renderers has no content.
> > > > >
> > > > > Since is random, this is hard to find, but seems the
> problem
> > is
> > > > > each time
> > > > > more easy to get.
> > > > >
> > > > > I suffer in compling TDJ from time to time. And the result
> is
> > > > that
> > > > > some
> > > > > times all compiles ok, and other times I get some
Navigator
> > > > > itemrenders
> > > > > without content (use to be per Navigator component, so all
> > > > renders
> > > > > in a
> > > > > control are affected), other times are TabBar items, other
> > > times
> > > > > are list
> > > > > item renders inside List playground, and so on. Some times
> > the
> > > > > problem
> > > > > affects many of the before mentioned controls, and other
> > times
> > > > are
> > > > > less of
> > > > > them.
> > > > >
> > > > > I think as TDJ grows, the problem increases, and I end
> > > compiling
> > > > > the same
> > > > > 2-3 consecutive times until I get the compilation right.
> > > > >
> > > > > For me this problem is one requirement to reach 1.0, since
> it
> > > > > reveals a
> > > > > cumbersome issue, that seems to increase with size of the
> > > source
> > > > > code
> > > > > involved.
> > > > >
> > > > > I want to ask here if others are finding this issue too in
> > > their
> > > > > projects,
> > > > > examples, etc..
> > > > >
> > > > > As well what could be the problem. Any theory?
> > > > >
> > > > > The problem should be in a compilation task that involve
> > > > > components that
> > > > > uses renderers inside. A based renderer control can
compile
> > ok,
> > > > > but the
> > > > > next one not, and the next could be right again...it's all
> > > > random.
> > > > >
> > > > > It seems a java thread issue where we need to sync better
> to
> > > > > endure things
> > > > > are build properly.
> > > > >
> > > > > Any idea or thing we could try to solve this problem?
> > > > >
> > > > > Thanks
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > >
> > > > >
> > > >
> > >
> >
>
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C091b10b063f747ec4b8608d7fa75da82%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637253256395538387&sdata=xO5EaBe5pz6F0%2BICaCefem2z8siG4%2FaZqw6Kqpo0VBg%3D&reserved=0
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Carlos Rovira
http://about.me/carlosrovira
