Log4OM

I tryed out the version that you send me (2.7.0.2), but it freezes in ~20-30 minutes in same way.

If you need more test, I am here for that.

G4POP wrote: 11 Jun 2020, 07:14
Hans
Not meant like that at all and you should know me better than that and I am offended that you would accuse me of being condescending!

You and other users would really have a cause to complain if we said 'Dont know mate, get on with it and revert to an old release' so please dont read things into my comments and think back to the 157 posts you have made and remember just how many times I helped you to resolve an issue!

Terry (and everyone else within earshot),

My apologies. That was a cheap shot, and without cause.

One of the things that I "cheerlead" about is the superb support team associated with Log4OM.

Then I go and give an undeserved jab in the ribs.

I have a fresh bottle of Belvenie 17. Next time you're in town I owe you a generous pour.

K0HB wrote: 13 Jun 2020, 03:55

G4POP wrote: 11 Jun 2020, 07:14
Hans
Not meant like that at all and you should know me better than that and I am offended that you would accuse me of being condescending!

You and other users would really have a cause to complain if we said 'Dont know mate, get on with it and revert to an old release' so please dont read things into my comments and think back to the 157 posts you have made and remember just how many times I helped you to resolve an issue!

Terry (and everyone else within earshot),

My apologies. That was a cheap shot, and without cause.

One of the things that I "cheerlead" about is the superb support team associated with Log4OM.

Then I go and give an undeserved jab in the ribs.

I have a fresh bottle of Belvenie 17. Next time you're in town I owe you a generous pour.

Thank you

My top priority is to address this issue. Unfortunately it doesn't happens on my system so it's really hard to catch.
It's probably a resource lock due to concurrency somewhere in the user interface as all background thread works flawlessy. If you can often reproduce the issue we can give you a test version

IW3HMH wrote: 13 Jun 2020, 11:38 My top priority is to address this issue. Unfortunately it doesn't happens on my system so it's really hard to catch.
It's probably a resource lock due to concurrency somewhere in the user interface as all background thread works flawlessy. If you can often reproduce the issue we can give you a test version

When I disable Trace mode, it freeze in a random time, then it is reproducible issue after all. You can give me all test version as you need. I will try all them.

I can say that I don't need to touch the Log40m UI to get it freezed. Normally I am using JTDX or leave PC untouched and I know the freeze when I watch JTDX and it isn't decode anything, then I can see the Mic windows icon blinking (the sound card mic icon), and if I try to scroll or click anything on Log40, it is freeze and I need to force close it, but is hard to get closed because the CPU is used 100% and it doesn't respond. I click with middle click on Log40 icon popup and in this way it show (slowly), the exit popup and I can close it.

(sorry for my english )

I had it happen just now with Trace on and generated a support request...now who do I send the zip to?

I can also try a test version.

I have another freeze with Trace. It happens right now in 2.7.0.2 version. I don't know if it is the same bug that I say before, but is a bug

Where I need to send you the log?

iw3hmh (at) log4om.com
Thanks

IW3HMH wrote: 14 Jun 2020, 09:03 iw3hmh (at) log4om.com
Thanks

I emailed it to you.

I think this is not the same bug as this topic, but is a bug anyway. However I desire that it fix both issues!!

I am testing the latest test version that you send me (2.7.0.6), and the 'Freeze' issue still there. I start the Trace mode and I am going to try to caught the Freeze issue. But without Trace, it still freezing.