southernfm
Active member
Hello,
This bug probably existed in prior versions.
We have backups that run on the same computer system that we use to log audio. At 2am for example, we start the backup process on the computer. This causes the RadioLogger application to 'freeze' and trigger the automatic restart of the logger software.
We detected this issue a couple of weeks ago and disabled the 'Restart the program if it crashes or hangs' setting.
After doing that, the logger recordings continue as normal (no interruption to the audio quality / recordings etc. even when our computer system is running backups).
I think the mechanism for detecting a hang/crash may need some tweaking.
We are working around it by disabling the feature so it isn't immediately impacting us, but others may have similar scenarios of not having a computer dedicated to logging audio only, and when those systems get busy it could falsely trigger an app restart.
This bug probably existed in prior versions.
We have backups that run on the same computer system that we use to log audio. At 2am for example, we start the backup process on the computer. This causes the RadioLogger application to 'freeze' and trigger the automatic restart of the logger software.
We detected this issue a couple of weeks ago and disabled the 'Restart the program if it crashes or hangs' setting.
After doing that, the logger recordings continue as normal (no interruption to the audio quality / recordings etc. even when our computer system is running backups).
I think the mechanism for detecting a hang/crash may need some tweaking.
We are working around it by disabling the feature so it isn't immediately impacting us, but others may have similar scenarios of not having a computer dedicated to logging audio only, and when those systems get busy it could falsely trigger an app restart.