Locks up when entering callsign

[KX7L]

I'm running Log4OM2 2.34.0.0, on Win 7 Pro SP1 (I know, I know, ancient OS, but it works). I have a peculiar problem with the program locking up for about a minute and a half while entering a callsign into the "Callsign" box at the upper left of the main window. After typing in the first 3 or 4 characters of the callsign, it quits responding to the keyboard or mouse, I get the blue blue spinning circle, and if I click in the window it will gray out and put (Not Responding) up in the title bar. Other applications (WSJTx, Chrome, etc) continue to work just fine during this time. Then after a minute or two, it comes back and all is OK.

This doesn't happen every time. Maybe once out of every 5 or 10 times I enter a callsign.

Any ideas?

Charlie KX7L

[G4POP]

I had the same issue years ago and it was Chrome that caused it because it is a resource hog even when apparently not running.

I removed chrome and the problem stopped

[KX7L]

I don't think it's Chrome. It did it today twice so far, the first time Chrome wasn't even running.

I notice this in the Program Notifications window (the yellow diamond with the "!" in it):
[23:17:44: WARNING SLOW RESPONSE TIME FROM EXTERNAL SOURCE: 106231.2108 MS]
[23:38:06: WARNING SLOW RESPONSE TIME FROM EXTERNAL SOURCE: 86060.097 MS]

This makes me think it has something to do with callsign lookup on QRZ.com. I have a reasonably good WiFI connection in the shack, and don't typically have a problem with response from QRZ.com, In fact once when this happened I looked up a callsign manually on QRZ using a browser while Log4OM was hung, and it went quickly on the browser. Here's my setup for "Info Providers: (I disabled HamQTH because it seemed pretty flakey).

I may just try disabling info lookup to see if the problem stops. It's cute, but not a critical feature for me.. I'm happy to let the other guy tell me his name

[KI5IO]

Charlie,

There are a few things you can 'turn off' to test to see if they improve performace.

1) Turn off VOACAP. Lots of data to/fro and can slow things down, especially with an older PC. Personally I never use VOACAP ... just don't feel it does much for me and my operating. Go to: Settings / Configuration / VOACAP Propagation

2) Turn off profile image: Go to: Settings / Configuration / Info Providers / Configuration Untic 'Show profile image ..."

3) As for not selecting HamQTH as a 'backup' Info Provider ... that won't make any speed difference. HamQTH is often quite speedy. QRZ is the location that tends to have slow responses. I get them from time to time as well. HamQTH is self-managed by OMs about the Globe and the data that is there is only from each individual OM who takes the time (if they choose) to fill it in.

4) Having an older/slower processor PC/laptop you will notice sluggish performance especially when you have a cluster connected and if there is a big participation event happening the clusters are slammed and that traffic will cause one's Log4OM to slow down. Especially with an older PC with a slower processor. I do a lot of filtering for my cluster feed at the CC-User APP that controls my feed from ve7cc or ae5e, etc.. I also adjust CC-User to only send me (as best as possible) only CW spots. I don't work SSB or any FTxx and such modes. I'm 100% CW in my shack

Anyway ... a few things to ponder.

[VK3AWG]

I have been having this issue for a while. I run Log4om on a Core I5 2.30Ghz , 16GB RAM. I have turned VOACAP off and Show Profile Image is also off. It doesn't do it all the time but when it does I have to shut everything down, reboot and restart everything. It will then be ok. Very strange.

Regards
Chris
VK3IK