Foe months, occasionally WSJT-X would stop decoding. The waterfall would indicate plenty of signals and the clock was in sync but it wouldn't decode. A restart of WSJT-X would not resolve the issue either. When it happened, no matter which version of WSJT-X was run, none would decode any signals..
The cause was traced to my Chrome browser. After not closing the browser for many days, Chrome continued to hog more and more memory. Eventually there came a point that so much memory was being used by Chrome that WSJT-X would not decode. The fix was to close Chrome, then restart it. With all of the URLs that previously were running started up again, WSJT-X would once again decode.normally. Just thought I'd share this with other Chrome users that may have experienced the same decoding failure. 73, Rich - K1HTV
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
