Endless loop bug on testing script
Endless loop bug on testing script
Hi Bernd,
I was testing something and found a bug. To reproduce, create a script :
- Loop Line : 0
- Add a single line. Mode : LoadTrack / Entry : X:\FileDoesNotExist.ext
- Click the Test... button
In my case it was resulting in an endless loop and had no other choice to kill the process ProppFrexx ONAIR.exe to exit.
Thanks,
Quentin
I was testing something and found a bug. To reproduce, create a script :
- Loop Line : 0
- Add a single line. Mode : LoadTrack / Entry : X:\FileDoesNotExist.ext
- Click the Test... button
In my case it was resulting in an endless loop and had no other choice to kill the process ProppFrexx ONAIR.exe to exit.
Thanks,
Quentin
Re: Endless loop bug on testing script
The script never returns a 'valid' entry, I guess this is clear...
However, it is not really an endless loop and you don't have to kill ProppFrexx.
Any script will end gracefully in the following conditions:
a) you click on the 'Cancel' button to abort the test
b) after 10 minutes of testing any test script execution is terminated automatically
c) after 100.000 script-line tries any test script execution is terminated automatically
d) test script returned more than 1 hour of tracks and was already looped
In your special case (always returning an invalid track), only the last condition d) is never reached.
But you are right, that this script testing/execution is too fast and that the log output is as such that much, that the UI response is very slow and not instant and the click on the Cancel button is as such effectively not really recognized on some hardware.
I will improve that in the next version!
I guess, that I will also lower condition b) and c) to 5 minutes and 25.000 tries.
Also note, that you might add the 'KeepStreamLoading' option to only eval the script-line, if it returns a valid and existing entry.
However, it is not really an endless loop and you don't have to kill ProppFrexx.
Any script will end gracefully in the following conditions:
a) you click on the 'Cancel' button to abort the test
b) after 10 minutes of testing any test script execution is terminated automatically
c) after 100.000 script-line tries any test script execution is terminated automatically
d) test script returned more than 1 hour of tracks and was already looped
In your special case (always returning an invalid track), only the last condition d) is never reached.
But you are right, that this script testing/execution is too fast and that the log output is as such that much, that the UI response is very slow and not instant and the click on the Cancel button is as such effectively not really recognized on some hardware.
I will improve that in the next version!
I guess, that I will also lower condition b) and c) to 5 minutes and 25.000 tries.
Also note, that you might add the 'KeepStreamLoading' option to only eval the script-line, if it returns a valid and existing entry.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Endless loop bug on testing script
Thank you for the explaination.
I am not sure to understand this point. What would do the 'KeepStreamLoading' option exactly in this case?
Re: Endless loop bug on testing script
The 'KeepStreamLoading' option adds an extra 'File.Exists' check and only adds the track, if it really exists. Without, even non-existing files will be used.
Just try it out ...
Btw, a new v4.4.4.5 is available, which adds the above optimizations!
Just try it out ...
Btw, a new v4.4.4.5 is available, which adds the above optimizations!
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Endless loop bug on testing script
Thank you very much for your prompt response!