You are not logged in.
My computer's fan is blowing like crazy. And it took some time figuring out why.
I ran htop, pressed F5 and saw that x-www-browser is running TWICE each taking up 29,7% of available memory.
The browser (i.e. iceweasel) takes up 60% of available memory!
What is going on?
--
Mod edit: Reflect the affected browser in the subject
Last edited by CooKiECruNChEr43 (2016-07-24 06:09:20)
Offline
The browser (i.e. iceweasel) takes up 60% of available memory!
What is going on?
You have the wrong browser, Iceweasel has been dropped and has several known vulnerabilities.
You should be using firefox-esr instead.
Run this command to change:
sudo apt upgrade
Post back if you still have problems afterwards
Offline
hmm I don't know if that's an iceweasel thing. I noticed that if I run the regular top command, it consolidates all of the firefox (and iceweasol back when I did use it) into one process. When I run htop, it gives you a much more broken down list of processes. I think (i'm not sure ) that this is done because FF splits different tabs as subprocesses, or atleast separates them. So htop shows each open tab as a different process of the same, main Firefox/Iceweasel process. Check the PID to see if my theory is right. I'll have to wait until I get my new VM installed to try it.
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
@HoaS
The menu command to run iceweasel actually runs firefox-esr (it is symlinked), but in htop it appears as "iceweasel".
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Hope this is relevant... This is the output screen shot I got from running htop when using the x-www-browser alternative call:
It's alt'd to run firefox-esr, but for me shows up at x-www-browser, as it should. Anyway, lots and lots of processes...
Below is when I run firefox-esr from tint2.... equally as many multiple processes...
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
^ This is normal output for default htop. In htop, go to Setuo(F2)>Display options and check "hide userland threads">Done(F10)
I don't care what you do at home. Would you care to explain?
Online
Great answers, thank you.
Offline
@damo: thanks :8
@HB: those are threads showing in htop rather than separate instances.
https://unix.stackexchange.com/question … ss-than-ps
@OP: Use this command to show how many Firefoxes are running:
pgrep -c x-www-browser
You can also use "Safe Mode" to debug FF problems:
https://support.mozilla.org/en-US/kb/tr … -safe-mode
Offline
@HB: those are threads showing in htop rather than separate instances.
https://unix.stackexchange.com/question … ss-than-ps
I *sort* of figured that... Well unfortunately I have no support for hyper threading so the use of a process creating multiple threads doesn't really help I'm assuming?
@CookieCrunch, how did you handle this? Did you do as madoromi suggests and just manually restrict it's memory?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
My -rather old computer - is still blazing. But I am still looking. For now, my question has been answered. Thank you for your answers. I consider it solved.
Offline