Radar plugin 5.5.0 spamming logfile

[GrahamC]

I notice subsequent to a 'hang' of open cpn that the radar plugin is somewhat verbose - just start opencpn with the plugin installed and no radar on.

2 days ago while using the plugin with my Raymarine C90W I noticed that the targets were no longer moving in the window and in fact opencpn was generally unresponsive so I closed the window - it took a log time to close but eventually did. I now have a 2GB logfile and .log.log.

I can't open the logfile as it is too big. Perhaps you can suggest a splitting tool so we can get to the bottom of this.
NO crash report files were generated this time -
I have plenty from other problems TBA.

I'm running Windows 10 on a UDOO x86 board. -
I have been running up to very recently 5.6.2 without problems.

[Hakan]

I think you need to find out what logs are flooding your file.
Start OCPN and stop it after a minute or two. Open the log file and look for repeated messages.
If you for any reason suspect radar plugin it would be caused by a "Verbose log setting" from any previous action. See the log for the verbosity setting:

MESSAGE radar_pi.cpp:281 Log verbosity = 0. To modify, set VerboseLog to sum of:..........

The default verbosity is "0". If changed to anything else is meant for a short time problem logging and will cause log flooding.
If you need to change the verbose log setting; close O, open opencpn.ini. Search for "VerboseLog" Set it to VerboseLog=0 and save the file.

[GrahamC]

I checked the .ini file and it was already set to VerboseLog=0.

I ran up OpenCpn and it started slowly filling the log file with radar connection timeout messages until I started the radar and put it in transmit mode using the C90W.
The log file then started growing fast - on inspection it is logging all the data received from the radar.

I have attached the logfile.log as I restarted opencpn and disabled the Radar plugin and the action of restarting copies the opencpn.log to opencpn.log.log and creates a new empty log file.