Log4OM

I am using Log40m2 since 2.6.0.0 version and I try it in two different PC (intel and amd), using same Windows 10 pro version (latest build: 1909), and in both PC I got same bug: after a random time, the application uses 100% cpu and it got freezes. I need to force close it to still using other applications.

Yesterday, I try the new update (2.7.0.0), and it takes 10 minutes to got freezes. The time to got the bug is random all times in both PC.

But, I try activate the Trace debug to send you the file and it not got freezes more times until next app reboot. Then I need to activate Trace to use the app. Using Trace, the app never got freezes.

I don't know how to make a Trace debug file because with it activated, the app doesn't freezes anymore.

I am using:
- Windows 10 pro build 1909 (64 bits)
- ICOM IC-7300 (with omnirig)
- Log40m2 2.7.0.0 (same bug in 2.6.0.0 and 2.6.1.0)
- JTDX 1.50 (64 bits)

EA7BYN wrote: 09 Jun 2020, 15:00 I am using:
- Windows 10 pro build 1909 (64 bits)
- ICOM IC-7300 (with omnirig)
- Log40m2 2.7.0.0 (same bug in 2.6.0.0 and 2.6.1.0)
- JTDX 1.50 (64 bits)

I have Win10 pro 64 bit latest, IC-7300 with Omnirig, Log4OM 2.7.0.0 and WSJT-X 2.2.1 and it runs 24/7 without any problem.

EA7BYN wrote: 09 Jun 2020, 15:00
I don't know how to make a Trace debug file because with it activated, the app doesn't freezes anymore.

I am using:
- Windows 10 pro build 1909 (64 bits)
- ICOM IC-7300 (with omnirig)
- Log40m2 2.7.0.0 (same bug in 2.6.0.0 and 2.6.1.0)
- JTDX 1.50 (64 bits)

Paco,

You can select the "Trace" level log in Configuration and run until your problem occurs again. Then some data might be available for you to view.

Albeit ... keep in mind that running Log4OM V2 full-time in Trace mode will very likely cause it to slow down in overall operation.

Check image below for setting Log Levels.

Hello Paco,

Using the same Softwares + JTDX but no freezes since i changed to a newer PC. On the older
one also no freezes after 2.4.x but overheating from time to time. Can you tell us what are your
PC-Setups (Processor, RAM, HDD or SSD) ...

My older one was AMD FX Quadcore with 4 times 3800 MHz clock and 8 GB DDR3 RAM and a 1TB
HDD but the system was "stoneold". Have cleaned all up with air pressure but nothing helps. The
new one is a DELL Optiplex 7010 with only 4 GB RAM and "only" 4 times 3400 MHz clock, but
1 TB SSD. Works fine.

Maybe your PC´s are old, having only HDD and a lot of Software which working in the background
that slow´s down ...

DK9JC wrote: 09 Jun 2020, 15:53 I have Win10 pro 64 bit latest, IC-7300 with Omnirig, Log4OM 2.7.0.0 and WSJT-X 2.2.1 and it runs 24/7 without any problem.

Can you share with me your Omnirig setup?

DF5WW wrote: 09 Jun 2020, 16:22 Hello Paco,

Using the same Softwares + JTDX but no freezes since i changed to a newer PC. On the older
one also no freezes after 2.4.x but overheating from time to time. Can you tell us what are your
PC-Setups (Processor, RAM, HDD or SSD) ...

My older one was AMD FX Quadcore with 4 times 3800 MHz clock and 8 GB DDR3 RAM and a 1TB
HDD but the system was "stoneold". Have cleaned all up with air pressure but nothing helps. The
new one is a DELL Optiplex 7010 with only 4 GB RAM and "only" 4 times 3400 MHz clock, but
1 TB SSD. Works fine.

Maybe your PC´s are old, having only HDD and a lot of Software which working in the background
that slow´s down ...

The PC is fine and I formated it last week, because I installed a SSD on it. But with SSD or HDD, the problem still here.

The system is clean right now with only a few services running at background, and I don't think that having 3 years old PC was the problem because with TRACE enabled, it doesn't uses 100% of CPU (and it uses more PC resources), and doesn't freezes.

The problem here is that I cannot trace the bug.

I've also seen this.

Have gone back to 2.6.1.0, waiting for 2.7.1.0 (or 2.8.0.0).

Unless we receive a support request in trace mode its very difficult for us to find issues so reverting to an older release does not help resolve this

It seems all users that having troubles were using JT modes.
I've added some code checks on 2 routines that may loop, but i'm still unable to replicate.
Working on...

The bug is fixed in Trace mode. Then, need to be checked the different things that has changed in this mode compared with Info mode, I think.

Trace mode is working fine.

I can do all try you need.