SB7.exe at 99%

[NewsArchive]

Hi Friedrich,

I'm noticing after I moved all my installs to SB7 that sometimes the command
line compiler seems to get stuck. It reports 99% CPU and just hangs there.
I run all of those compiles from BA, but it just calls it via the command
line, like it has always done and I have never seen this problem until
recently. I'm on build 7.2.3062. I'm _not_ sure if this started happening
with SB7 or if it started with some update this summer. In this particular
project that I'm working on now I have 3 calls to the SB compiler, one to
code sign several exe/dlls and then two that build a full install and a web
update. They are called one after the other so I'm going to add a wait
action between them. Perhaps it is called to quickly and the previous
process doesn't have time to terminate before the next one is started. But
if you have any other ideas, please let me know

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> I'm noticing after I moved all my installs to SB7 that sometimes the
> command line compiler seems to get stuck. It reports 99% CPU and just
> hangs there. I run all of those compiles from BA, but it just calls it
> via the command line, like it has always done and I have never seen
> this problem until recently. I'm on build 7.2.3062. I'm _not_ sure if
> this started happening with SB7 or if it started with some update this
> summer. In this particular project that I'm working on now I have 3
> calls to the SB compiler, one to code sign several exe/dlls and then
> two that build a full install and a web update. They are called one
> after the other so I'm going to add a wait action between them. Perhaps
> it is called to quickly and the previous process doesn't have time to
> terminate before the next one is started. But if you have any other
> ideas, please let me know

I can't remember any compiler modification that would cause this to happen.
Unfortunately (or fortunately, depending on how you look at it <g>), we have
not received any similar report nor did I ever see this happen here (we are
doing more than 150+ test command line compilations on a daily basis). One
of our customers is doing 1,000 nighly command line builds and the server
did not report any problem (that system is in production for 11 months now).

Does the compiler .log give any more information? Is the .exe already fully
generated and code-signed when it "hangs"? Do you use .spc/.pvk to
code-sign? Perhaps it's caused by a very specific Windows update and/or
protection software product!?

Friedrich

[NewsArchive]

Hi Friedrich,

> Does the compiler .log give any more information? Is the .exe already fully
> generated and code-signed when it "hangs"? Do you use .spc/.pvk to
> code-sign? Perhaps it's caused by a very specific Windows update and/or
> protection software product!?

No, the compiler log is ok. I.e. the compile seems to finish properly. I'm
using .spc/.pvk. This is running on an older computer with XP Home SP3 and
it should be up to date. Normally I don't notice this until the fan in the
PC kicks into high gear So I'm not sure if there is a specific script
that is being compiled when this happens. However, after adding a 2 second
delay between the calls to the compiler in my BA script I have not seen this
(did quite a few builds today as I'm testing new/modified installs, probably
about 20 and each one calls SB7 3 times) I'll let you know if I find
anything useful

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

> update. They are called one after the other so I'm going to add a wait
> action between them. Perhaps it is called to quickly and the previous
> process doesn't have time to terminate before the next one is started. But
> if you have any other ideas, please let me know

After adding a 2 second delay between the calls to the SB7 command line
compiler I have not had a single instance of this all day. I've probably
run about 20 builds after I did the modification, each calling 3 SB scripts.
I will be on the lookout for this in the future and will let you know if I
discover anything further

Best regards,


--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>> update. They are called one after the other so I'm going to add a wait
>> action between them. Perhaps it is called to quickly and the previous
>> process doesn't have time to terminate before the next one is started.
>> But
>> if you have any other ideas, please let me know
>
> After adding a 2 second delay between the calls to the SB7 command line
> compiler I have not had a single instance of this all day. I've probably
> run about 20 builds after I did the modification, each calling 3 SB
> scripts.
> I will be on the lookout for this in the future and will let you know if I
> discover anything further

That's very interesting. Thanks for the information!

In 7.3, there is a modified function to close threads (under certain
corcumstances, the IDE "locked" when opening/saving/closing projects).
Perhaps these issues are related.

Friedrich

[NewsArchive]

Hi Friedrich,

> In 7.3, there is a modified function to close threads (under certain
> circumstances, the IDE "locked" when opening/saving/closing projects).
> Perhaps these issues are related.

Could be. I do not recall this ever happening in SB6 but I'm sorry to say
that I have not paid attention to when this started in SB7. What I do know
is that the install _seems_ to be completed when the process hits the
endless loop or whatever it is. It also seems that subsequent calls proceed
normally (everything just seriously slows down<g>) I also have not got
reports of this happening with any BA users so maybe there is something on
my computer causing this.

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>> In 7.3, there is a modified function to close threads (under certain
>> circumstances, the IDE "locked" when opening/saving/closing projects).
>> Perhaps these issues are related.
>
> Could be. I do not recall this ever happening in SB6 but I'm sorry to say
> that I have not paid attention to when this started in SB7. What I do
> know is that the install _seems_ to be completed when the process hits the
> endless loop or whatever it is. It also seems that subsequent calls
> proceed normally (everything just seriously slows down<g>) I also have
> not got reports of this happening with any BA users so maybe there is
> something on my computer causing this.

I think it's the function (in SB5, SB6 and SB7) that terminates the open IDE
threads and this goes into an endless loop. There is a slightly modified
function in SB73 to terminate threads and we'll see if this helps

Friedrich

[NewsArchive]

Arnor - I have this from time to time but did not report it as I thought it
was just "one of those things".

HTH

John Fligg

[NewsArchive]

Hi John,

> Arnor - I have this from time to time but did not report it as I thought it
> was just "one of those things".

Ok, so it's not something on my machine<g> Do you only see this when you
compile from BA? I don't recall ever seeing this when compiling from the SB
IDE, so I presume this is something in the SB command line compiler.

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

> action between them. Perhaps it is called to quickly and the previous
> process doesn't have time to terminate before the next one is started.

Just did it again! It doesn't stop subsequent SB7.exe processes to start,
but things kind of slow to a crawl<g>

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php