It seems throwing without a catch block inside a scheduled environment has an erroneous loop / failure to exit the script completely.
Throwing in this scenario stops execution of the script but will spam errors (to both -showScriptErrors and the RPT file).
Note that returning to the escape menu (pausing the simulation) appears to end the error spam.
Tested on following version:
["Arma 3","Arma3",194,145977,"Stable",false,"Windows","x64"]
[] spawn {
uisleep 3;
systemChat "test1";
throw "test";
systemChat "test2";
}23:05:32 Error Unhandled exception: "test"
23:05:32 Error in expression < spawn {
uisleep 1;
systemChat "test1";
throw "test";
systemChat "test2";
}>
23:05:32 Error position: <throw "test";
systemChat "test2";
}>
23:05:32 Error Unhandled exception: "test"
23:05:32 Error in expression < spawn {
uisleep 1;
systemChat "test1";
throw "test";
systemChat "test2";
}>
23:05:32 Error position: <throw "test";
systemChat "test2";
}>
23:05:32 Error Unhandled exception: "test"
23:05:32 Error in expression < spawn {
uisleep 1;
systemChat "test1";
throw "test";
systemChat "test2";
}>
23:05:32 Error position: <throw "test";
systemChat "test2";
}>
23:05:32 Error Unhandled exception: "test"
[Continues Many Times]
I've updated this to major as when it happens, it causes huge log spam which can affect server performance. We had one error from this bug that resulted in 1.5 million log lines for a half hour period.
Cannot repro, I get one log print in 2.01
And as far as I'm aware that code wasn't touched since your last comment in february.
Can confirm in 2.00.146773
Please note, that it ONLY happens when in a mission. Running the script from the debug console in 3den only returns the error once.
Please note, that it ONLY happens when in a mission. Running the script from the debug console in 3den only returns the error once.
I cannot confirm that on 2.01. Spam happens both in Debug Console and during scenario.
noLogs = false;
showScriptErrors = true;