Hi all,
Several ( many) years back I had the same symptoms with WSPR in that it failed
after a few days
and lasted longer running on machines with more memory.
The problem was, not freeing up Virtual Memory after a decode cycle.
On Windows systems, the problem did not surface, only on Linux. T
Would someone please point me to an explanation of how the dB report of a
received FT8 signal is derived. My recollection was that it was independent of
the actual receiver bandwidth but simple experimentation shows that's not true.
Simply narrowing the receiver bandwidth on a signal of intere
I'm seeing it too, just listening on 40M WSPR and reporting to wspr.net, and it
stops working probably once a day. The waterfall stops moving and decodes stop
happening. I have to stop and restart WSJT-X
I'm running v2.3.1 0e7224 if it matters. I've seen similar behavior on
previous release
