Log4OM

version 2.25.00 suddenly takes up 100% resources
As per the title suddenly and for no apparent reason the processor is occupied by 90% to 100% of its capacity.
Checked with ctrl+alt+cancel and looking at running tasks. This results in a noticeable delay, when you are using other programs to communicate a delayed release or push-to-talk for transmit/receive. I don't know the same thing happens to others but I'm forced to stop log4 from running tasks and restart it.
Win 10 system
I5 processor at 3.40mhz
memory 16GB
2 SSDs 500GB
With the previous version and many other previous ones it had obviously never happened always using the same system previously described.
Thanks everyone, hope I'm not the only one having this problem
Enzo IU8MOA

ITALIANO

Come da titolo improvvisamente e senza apparente ragione il processore viene occupato dal 90% al 100% delle proprie capacità.
Controllato con ctrl+alt+cancel e guardando i task in funzione. Questo comporta un notevole ritardo, quando stai usando altri programmi per comunicare ad un rilascio ritardato o un inserimento del ptt per la trasmissione/ricezione. Non so ad altri succede la stessa cosa ma sono costretto a fermare log4 dai task in esecuzione e riavviarlo.
Sistema win 10
processore I5 a 3.40mhz
memory 16 Gb
2 ssd 500gb
Con la versione precedente e di molte altre precedenti non era mai successo ovviamente utilizzando sempre lo stesso sistema precedentemente descritto.
Grazie a tutti, sperando di non essere il solo ad avere questo problema
Enzo IU8MOA

I have the same problem. This seems to occur after the program has been running for a few hours. I have been shutting the program down and then restarting every few hours to get around this. When it happens my computer slows to a crawl.
Brian VK5UW

Have you tried disabling some choices in the config 'Performances' menu?

I have also been experiencing this since the update. I believe something is happening when WSJTX (or FTDX) sends over data.
I'm running FTDX on a seperate Ubuntu computer and I'm only using Windows 10 to host Log4OM. My suspension is .NET framework.
W10 is 21H2, Ryzen 7 8-core, 48 GB RAM, NVIDIA GeForce GTX 1060 6GB. The computer is fairly idle otherwise. Like the OP said, it may run fine for an hour or a day but you can guarantee when your trying to log that all-time-new-one or new-DX-on-band is when <edit> I find the CPU has been/is locked at 100% and Log4OM is unresponsive. Sometimes I'm actively using Log4OM to view worked before or DXCC status and it becomes unresponsive.

I have turned off VOACAP. So far have not had any lockups. Too soon to be sure yet. I will post if it freezes again.

Brian
VK5UW

vk5uw wrote: 24 Dec 2022, 23:45 I have turned off VOACAP. So far have not had any lockups. Too soon to be sure yet. I will post if it freezes again.

In the VOACAP configuration screen one can also switch between 2 or 4 digits locator. The default is 2 but in case it was set to 4, try 2 to see if the feature can remain enabled/available and still clear the problem.

Since turning off VOACAP I have not had any further instances of 100% CPU. I have not yet looked at the 2 or 4 digit locator setting yet as I didnt want to introduce any other variable. I will look at the locator setting in a few more days if everything continues to work.

Thankyou you everyone involved in making this excellent sofware available to us all.

Brian
VK5UW

I have the same problem here. 100% resources taken by log4om.

I have wsjt-x running at the same time and I leave log4om running for logging using UDP.

Seems to me it happens when TQSL needs to be updated ? Not quite sure. I will see later.

I will try to turn off voacap next ...
but my locator setting was already set at 2 digits before, the default value.

73, de Stef ve2owl

I have the same with version 2.25. After a few minutes, the CPU load reaches 100%. Restarting the application helps for several minutes and the problem returns. VOACAP is disabled, but the problem persists.
Windows 10 (newest version) with CAT interface. I`m using also JTDX.

Tom SQ4BJA

I have the same and when I close the program an error pops up: Runtime error 217 at 00457D45

I tried to solve it with SFC and Dism Scan. Restart and it is okay. After an hour it's back.

I use the latest version with windows 11. Next step would be re installation of Log4OM V2.

73, Roland PE1PIN