News for hackers. Stuff that matters.
Re:Firefox 58 by adpirz on Tuesday January 23, 2018 @02:20PM (#16216582)
FF 57 was much snappier on my Mac than on Chrome, but it occasionally turned into a CPU hog and got the fans spinning full blast. Did anyone else experience that?
Re:Firefox 58 by tzs on Tuesday January 23, 2018 @04:33PM (#16217921)
I've occasionally seen something named "FirefoxCP Web Content" taking 90+% of a core, mostly on Reddit.

Most of the time when it happens on Reddit it stops if I turn on uBlock Origin and refresh the page. Sometimes, though, it still happens even after that.

Re:Firefox 58 by executesorder66 on Wednesday January 24, 2018 @02:45AM (#16221072)
> it stops if I turn on uBlock Origin and refresh the page

Why do you turn it off in the first place?

Re:Firefox 58 by tzs on Wednesday January 24, 2018 @03:42AM (#16221285)
Reddit ads are at fixed positions on the page and don't have sound or motion. They generally provide no distraction, unless the content actually catches my attention because it is something I'm actually interested in. Their ad targeting is good enough that I actually am interested in a fair number of them.

Unless it turns out that the high CPU usage is the fault of the ads (which I've not been able to prove), Reddit's ad system is the kind of ad system we should be encouraging, so I don't block them.

Re:Firefox 58 by rs999gti on Wednesday January 24, 2018 @10:10AM (#16223230)
I was looking for this part of the thread. I'm on Windows 10 on an i7-6600U laptop with 16GB RAM and a SSD.

FF57 spiked my cpu to 100% most of the time and Netflix was really laggy. I went back to Chrome because it only uses 10-20% CPU with regular usage.

In FF57, I was using default performance and browser settings.

Re:Firefox 58 by available on Tuesday January 23, 2018 @02:28PM (#16216678)
Yes, I simply couldn't use it because it drained my macbook battery too quickly. I just updated to 58, but it seems to still be a problem.
Re:Firefox 58 by apazzolini on Tuesday January 23, 2018 @03:22PM (#16217281)
Same here - first thing I did when v58 came out was check to see if CPU usage was lowered, which it unfortunately wasn't.

I see no reason why CPU activity should spike to 20% every few seconds with one blank tab open and no extensions enabled.

Re:Firefox 58 by jakecopp on Tuesday January 23, 2018 @06:36PM (#16218963)
To save battery life I'm trying to switch to Safari (from Chrome -> Firefox) but container tabs in Firefox are amazing - the ability to automatically open a domain in a container is perfect.

Is it possible to whitelist cookies per domain in Safari?

Re:Firefox 58 by mikko-apo on Tuesday January 23, 2018 @04:11PM (#16217741)
Only time when I noticed my fans revving up was when I went to a site that tried to mine some bitcoins.

Closing the tab reduced the cpu usage to normal levels.

Re:Firefox 58 by srcmap on Tuesday January 23, 2018 @06:42PM (#16218998)
FF should put up a "red flaming" icon on the tab with high CPU usage - similar to audio icon on the tab with audio output.