Command line compiler process gets stuck

[NewsArchive]

Hi Friedrich,

One thing that I have run into from time to time is that when the command
line compiler is run from Build Automator, it doesn't unload itself but
keeps running. Subsequent calls to it fail. I had an email from one of my
testers this morning report something similar now with my latest build and
the latest SB build, where the call to SB returns with exit code 1. I'm
going to give him a debug build which will give me some more information but
in my experience the SB command line compiler process gets "stuck" and keeps
running, sometimes gobbling up CPU like it is stuck in a loop. The previous
build, after which it gets stuck, is completed, so it doesn't get into this
situation until it is done compiling.

Any ideas for me to try out?

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
https://twitter.com/#!/Icetips -
https://www.facebook.com/pages/Icetips-Alta-LLC/177947342793

[NewsArchive]

Hi Arnór,

>
> Any ideas for me to try out?
>

To be honest, I don't know. I never ran into this and I don't have any
similar reports. When we test new builds, we automatically compile 100+
test scripts (including "fake" failed scripts) and it never went into an
infinite loop here :-(

What does Build Automator do to "wait" for sb7.exe? Perhaps this "locks"
the sb7.exe? Does it also lock if you do not display the progress bar in
the command line compile?

Nothing changed in the command line compiler for years.

Friedrich

[NewsArchive]

Hi Friedrich,

> To be honest, I don't know. I never ran into this and I don't have any
> similar reports. When we test new builds, we automatically compile 100+
> test scripts (including "fake" failed scripts) and it never went into an
> infinite loop here :-(
>
> What does Build Automator do to "wait" for sb7.exe? Perhaps this "locks"
> the sb7.exe? Does it also lock if you do not display the progress bar in
> the command line compile?

See my post on October 17, 2010 "SB7.exe at 99%" I can see there that I
fixed it with a 2 second delay between the calls to SB.

This happens rarely. It doesn't happen when SB is run from a command line
only when run from BA. I have a #copy statement in all my installs to copy
the finished install to my LAN server. I have only had ONE BA customer
report this as far as I can tell.

Most of the time I don't even realize what happened until I hear the fans
start blowing full speed in the machine as the CPU has been working at 100%
for a while<g> Then I find SB7.exe at the top of the CPU list.

I don't have this problem with any other program, but SB is the only program
that I may run one after the other to create the install and web install!
Maybe I just need to add a 1 sec delay at the end of the SB action to give
it time to shut down gracefully. I'll do that and see if this comes up
again.

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
https://twitter.com/#!/Icetips -
https://www.facebook.com/pages/Icetips-Alta-LLC/177947342793