Radiologger 3.3.3.0 bug

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.

southernfm said:

I think the mechanism for detecting a hang/crash may need some tweaking.

Click to expand...

It merely checks if the software is still responding - that is, the main window is able to receive user input. In your case, I suppose the freeze is caused by backup software, e.g. it locks some system resource that RadioLogger depend on.

Can you please send us bug reports to support@djsoft.net? Bug reports are located in the RadioLogger settings folder (you can open it from "RadioLogger" menu), files are called "bugreport_*.txt"

djsoft said:

an you please send us bug reports to support@djsoft.net?

Click to expand...

There are no bug reports, only log.txt logger.xml logger.xml.bakand an archive folder

I do have these entries though:

[2020-04-01 02:00:00] Recording started
[2020-04-01 02:01:52] RadioLogger started
[2020-04-01 02:01:53] Recording hour 02:00-03:00
[2020-04-01 02:01:53] Recording started

[2020-03-01 02:00:00] Recording started
[2020-03-01 02:01:33] RadioLogger started
[2020-03-01 02:01:33] Recording hour 02:00-03:00
[2020-03-01 02:01:33] Recording started

[2020-02-01 02:00:00] Recording started
[2020-02-01 02:02:21] RadioLogger started
[2020-02-01 02:02:22] Recording hour 02:00-03:00
[2020-02-01 02:02:23] Recording started

As an example. 2am is when our backups start

Thank you for the information. In this case, it seems that backup process interferes somehow with RadioLogger, e.g. by locking certain files or hogging all CPU resources. I don't think it's a problem with RadioLogger, so at this point there's nothing to fix.