With me is the combination of Firefox and realtime scanning those two running block everything specially when firefox is standby (no window open in browser)
Leo Bally Ok8leo > On 9 Nov 2018, at 06:24, Jim Shorney <[email protected]> wrote: > > > You haven't seen the way I browse. I can bring a quad core i5 with 16G RAM to > its knees with 64 bit Waterfox. Easily. If I leave Firefox on the Kubuntu box > sitting on a couple of PSKReporter pages I can watch the memory usage creep > up. > It's the only thing I've run on the 16G laptop that's ever hit swap. > > 73 > > -Jim > NU0C > > On Thu, 8 Nov 2018 22:52:57 -0600, Stan Gammons wrote: > >> lol! >> >> Firefox doesn't seem to eat up all 16 Gb of memory I have in this >> Kubuntu 18.04 machine. Actually it's probably more like 8 Gb available >> with VirtualBox running a win7 VM. >> >> 73 >> >> Stan >> KM4HQE >> >> >> >> On 11/8/18 10:41 PM, Jim Shorney wrote: >>> Web browsers leak memory. I've come to believe that it is a fundamental law >>> of >>> the universe that a browser will expand until it consumes all available >>> memory. >>> >>> 73 >>> >>> -Jim >>> NU0C >>> >>> >>> On Thu, 8 Nov 2018 22:05:19 -0600, Stan Gammons wrote: >>> >>>> 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 > > -- > > "Good men dont need rules. Today is not the day to find out why I have so > many." - Doctor Who > > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
