SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Lately I have been using Firefox like i normally do on a day to day basis, however, it has been freezing to the point that if I want to use firefox again I have to restart my system. This mostly after I view a video. When I do finally get FF off my screen, the PIDs are still in place and cannot be killed. i.e. kill <firefox PID> does nothing.
Here is some info:
FF 3.0.8
Adblock+
NoScript
Linkification
Java 6_11
Flash 10 (or whatever the latest one is)
firebug
Download Status Bar
And i think that is all. This just started happening about 1-2 weeks ago when 3.0.7 went to 3.0.8 and I changed some hardware in my system.
Hardware changed
Motherboard, CPU, PSU
I went from an AMD X2 6000+, DFI 790FX/SB600 to a C2D E5200 and DFI DK X48-T2RS Plus. I recompiled my kernel for everything to make sure it runs correctly.
I have that sort of lockups when I close a tab that has been used to view a long video file (say, an hour long or more). Maybe there's a problem with cleaning the cache file, I don't know. But it has been bothering me, too, i have to do 'kill -9' each time.
How long have you waited to see if it settles down?
To give you an idea of what I'm thinking; If FireFox is caching a large video, which can be 4 to 6 gigs, it would take 10 to 20 minutes in just raw disk I/O time to purge a cache database. I can tell you the XP version of FF does this purging after close, but it closes the GUI and does it completely as a low priority background task.
Since SeaMonkey is very similar, you might want to try that browser and see if it does the same thing.
I should also point out that Firefox has their own excellent support forums. From Firefox click help, release notes. I think you'll see the various options from there. Or just click on this -
So, you mean it freezes like this after a flash video ? If so, then it's obviously flash that causes it. If you use mplayer-plugin that could also cause it.
Last edited by H_TeXMeX_H; 04-22-2009 at 10:56 AM.
In my case it freezes after closing tabs with large video files cached (actually it sometimes freezes, sometimes not, happens about 50% of the time). I'm sure I've waited long enough to conclude that it is a freeze. It should delete the file /tmp/FlashXXXXX after closing the tab with the player. When there's a freeze the file is not deleted.
What is a reasonable sized cache for firefox to have?
I have this same problem and can't even kill it with a kill -9...
I also have a similar problem...not sure if it is related where flash videos won't play if the firefox application has been running for a while. If I want to watch youtube or something, I have to restart firefox. Does this sound more and more like a cache problem?
Last edited by spaceballs; 04-24-2009 at 12:06 AM.
Appears the 32bit version has the same problem. All of the following from the following url. Strongly motivated individuals may want to register on the adobe site to enter your comments regarding the bug, as they seem to look at that information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.