I am currently running WSJT-X 2.7.0~rc6 from backports on Bookworm. For quite some time, though I've not documented over how many releases, I have noticed that a long running WSJT-X process will get sluggish or simply stop decoding certain minute segments. As an example, I may have started WSJT-X yesterday some time and have mostly been in FT8 mode with a bit of time in FT4 on 15 and 80m. At various points I stopped the decoder to operate voice nets, etc. Upon returning to FT8 on 30m a little while ago I noticed that the program was not decoding traffic from the 00 and 30 (even) segments but was decoding on the 15 and 45 (odd) segments. Most of the time when I see this happen it decodes the even and not the odd segments. When the program gets into this state, initiating a transmission usually results in a delay of 2 to 3 seconds before audio is sent to the radio though PTT assertion is generally immediate. In all cases, restarting the program restores proper operation. Perhaps this has to do with portions of the program getting paged out to swap over time? If so, it doesn't seem like the program is ever completely returned to RAM and remains in kind of a zombie state until it is restarted. I suppose if I closed and opened the program each time this wouldn't be an issue. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
Attachment:
signature.asc
Description: PGP signature