Log4OM

Hi. I hope someone can help with this. I was running 2.7 and it used to freeze about once a day. I upgraded to 2.8.0 and it freezes about 3 times an hour. I never had a problem with freezing with versions before 2.7
I have the log level set to trace. I use JTDX V2.1.0-rc151_32A and JTalert V 2.16.8 on a windows 10 Home Version 1909, i7-8700 Dell XPS 8930, with 16GB RAM
Thanks, Colin MM5AGM

Colin,
There seems to be a small subset of users having this issue and we are working hard to resolve it.

Fortunately we are getting a lot of help from John VK7XX, his mate and a couple of others in repeatedly testing debug releases, we will find the issue soon so bear with us.

Many thanks.
One thing I forgot to mention was that it seems it's only the user interface that freezes. It continues to log contacts even though the "Recent QSO's" doesn't update. When you end the Log4OM process in task manager, the only way to stop it, the next time you open the program the "Recent QSO's" has been updated.
Colin MM5AGM

mm5agm wrote: ↑08 Jul 2020, 11:01 Many thanks.
One thing I forgot to mention was that it seems it's only the user interface that freezes. It continues to log contacts even though the "Recent QSO's" doesn't update. When you end the Log4OM process in task manager, the only way to stop it, the next time you open the program the "Recent QSO's" has been updated.
Colin MM5AGM

Now that is interesting!

Terry,

I am also having this same issue.

Using Log4OM 2.8.0, WSJT-X 2.2.2, and Win 10PRO.

The Log4OM GUI freezes (does not accept any input or mouse clicks), but it does NOT show the usual grey "Not Responding" title line. Also, the "input" window does not reflect the ongoing WSJT-X QSO. The freeze isn't predictable -- might be after 2 QSO's, or after 100.

I have noticed it several times when paired with WSJT-x (which I use often), but I haven't seen it when operating N1MM+. (Perhaps it does occur, but I just don't recall that it has. I will pay more attention.)

You must use the task manager to stop Log4OM.

When you restart Log4OM, you find that the log HAS captured the QSO's which were made during the "frozen" period.

Regarding my last, and N1MM+...

I just completed a 1-hour long mini test on N1MM+.

The GUI froze about 15 minutes into the session, but the QSO's for the remaining 45 minutes were captured in the log.

It looks like the freeze only occurs when Log4OM is listening to any UDP port.
I have disabled all UDP ports and started logging using the ADIF monitor function.
I had no freeze since then, but freezes come at irregular interfals, so i don't know for sure yet.
Can someone else confirm this?

73, Peter, PE4A.

Disabled UDP ports. Was looking good but froze after 2 hours.
Colin MM5AGM

Yes, colin,
it took much longer here, but it was frozen when i came back to the shack.
I'm running out of ideas.
Thanks for your help.
73, Peter

Another way to describe this issue....

....it is as though another "hidden window" has seized focus.