locked AutoIt Error


Stewart Wilkinson
 
Edited

Just cam back in the shack to find:




JTAlert 2.10.7 with WJST-X v1.8.0 running FT8 on 50.313

After clicking OK JTAlert went to Not Responding and Windows eventually closed it.


Michael Black
 

That happens every once in a while....a long standing bug in the compiler unfortunately.

de Mike W9MDB


On Friday, December 15, 2017, 9:01:51 AM CST, Stewart Wilkinson <stewart.g0lgs@...> wrote:


[Edited Message Follows]

Just cam back in the shack to find:




JTAlert 2.10.7 with WJST-X v1.8.0 running FT8 on 50.313

After clicking OK JTAlert went to Not Responding and Windows eventually closed it.


JTAlert Support (VK3AMA)
 

On 16/12/2017 1:58 AM, Stewart Wilkinson wrote:
Just cam back in the shack to find:




JTAlert 2.10.7 with WJST-X v1.8.0 running FT8 on 50.313

After clicking OK JTAlert went to Not Responding and Windows eventually closed it.
_._
Once JTAlert throws this type of error, there is no recovery, it is fatal, the program needs to be closed and started again.

There are no undeclared variables in the JTAlert code. The compiler would refuse to create the JTAlert executable if that was the case. The error type and line number are both incorrect and will vary. This type of error happens infrequently for a very small number of people. In most cases they will experience the error only once or twice, Unfortunately, the root cause of these errors is unknown and to-date I have been unable to reproduce the error.

The root cause is the aging compiler used for JTAlert V2. The new JTAlert V3 (still some months away from release) uses a new modern/standards compliant compiler, a different language and is a total rewrite of the JTAlert code making heavy use of asynchronous object-oriented code with extensive error-trapping and reporting. These type of  unexplained errors will be a thing of the past.

de Laurie VK3AMA
   
de Laurie VK3AMA
   


NA2NY - John Hart
 

Haven’t seen that error since moving to newer W7 machine, saw it a lot with XP machine.
 
John NA2NY


JTAlert Support (VK3AMA)
 

On 17/12/2017 12:59 AM, na2ny_fe1 via Groups.Io wrote:
Haven’t seen that error since moving to newer W7 machine, saw it a lot with XP machine.
 
John NA2NY

John,

Thanks for the feedback.

It is not always the case, but the majority of these reports that I get have one or more things in common, running XP (usually on aging hardware), limited installed Ram and underpowered CPU (one or two core). Often the installed Ram is barely sufficient for XP alone without overburdening it with cpu intensive FT8 decoding and CPU/memory heavy HRD installs.

Heavy CPU/Ram usage on underpowered PCs is typical for this type of unmanaged JTAlert error.

de