I've seen the same thing happen with Chrome and a web app we have at
work. The app gets slower and slower and slower as the browser hogs up
more and more memory. Not sure which one to point the finger at. The web
app or Chrome. Were you using any web app at the time? I don't use
Chrome at home. I use Firefox. Have you tried to duplicate the problem
with Firefox?
73
Stan
KM4HQE
On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote:
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
