SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey guys. I'm running slackware 11.0. I've tried both E16 and E17 desktops and the problem continues to happen on both.
I'm running FF 2.0 from the slackware repository. I leave it up and it seems every 3 days, the CPU will peg at 100%. Using top/htop, it shows the firefox-bin process using 90% or so of the CPU. And this is completely at idle.
agree with that
i'm using Firefox package from Mozilla (not from Slackware package) and i experience the same thing. It consumes too much resources and it didn't only happened in Linux, but in Windows also
i hope Firefox 3.0 will less hunger for memory consumption
Why do I need it open that long? Because it's the most used application on my machine. I drop it onto desktop 2 and just leave it open. No reason to close applications that I'll just have to reopen the next time I sit down in the chair.
What's strange is that the CPU usage starts at 0 for the first day or so. Then all of a sudden it spikes to 100%. Resource hog I can understand. But it shouldn't be processing anything. I fail to see how sitting on www.google.com for any length of time would cause CPU usage, let along 100% usage.
FWIW i've noticed FF2 will eat all my memory, then swap, so the system starts swapping ... that usually raises the CPU after a day or two. I'm considering rolling back to 1.5 ... as yet I can't decide if there are any features in 2 that i need.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6469 rberquis 17 0 83856 80m 19m R 88.1 16.1 3005:10 firefox-bin
6473 rberquis 11 0 83856 80m 19m S 10.3 16.1 223:29.66 firefox-bin
CPU is once again pegged. As you can see, the swap space is untouched.
Edit: I'll try disabling forecastfox when I get home.
Edit: another update
OK, so after 2 days of googling "firefox CPU usage" and getting nothing, I took your advice and searched for "forecastfox CPU usage". BAM, answers. Several website including forecastfox's own website state the following:
We are aware of the CPU Usage Bug. This appears like it may be a bug in Firefox's progressmeter implementation. We are currently tracking it here: http://bugs.ensolis.com/show_bug.cgi?id=200 and we believe it will be fixed with Firefox 184.108.40.206.
I've got the same issue as you and I too have forcastfox installed. The only other extension I have installed in common is download statusbar.
I leave firefox running a lot because I'm often in the middle of doing something, 8 or 9 tabs open and then get called away. I might not get back to it for a couple of days. Until I finish my research or whatever I'm doing, why would I close out firefox ? It should be able to run indefinitely.
Are you using Firefox 2.*?
You can restart your closed session by selecting this option in Preferences --> General --> When Firefox starts "open my windows and tabs of the previous session" (could be slightly different, my FF is Dutch )
Another thing that can cause this behavior is a corrupted FF-profile. Create an new one, move important stuff from you old to your new profile (bookmarks, passwords etc.) but NOT your extensions/themes! Of course, then you will have to install those extensions again.
What you're describing is a classic memory leak, and yes, it can eat up processor cycles. I agree with sn9ke_eyes it should be able to run indefinitely, but sometimes programs don't work that way. This is a well known problem with ff too. I don't use forcastfox, but I have two other extensions in common with you and I've had the same type of problem on 1.5 I know this isn't much of an answer but all I do is quit firefox for a minute and then reload - no more memory leak!