Closed Bug 495581 Opened 15 years ago Closed 15 years ago

Firefox 3.0.10 Run away memory usage and unable to fully shut down Firefox

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dgc.49.08, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) This problem is very similar to the one posted in bug 467939. I have noticed ever since Firefox 2 and every version since to current version 3.0.10 that Firefox continues to use up more and more memory. After about 1 hour or more of running Firefox has used up all my available memory and when I try to shut it down to clear out the memory, Taskmanager shows that it's still in memory. Only way to get rid of Firefox is to use taskmanager to remove it. One of my ZoneAlarm firewall configuration allows me to block java and javascripts from specific webpages. I noticed that when I did this, the problem with Firefox using up memory seemed to decrease significantly. I was able to run Firefox all day then and never had to shut it down. As I said, this seems to be a problem that has been there ever since FF2 came out and has never been fixed despite my numerous reports on the problem. Reproducible: Always Steps to Reproduce: 1. Just run Firefox normally for long periods of time. 2. Any amount of time over 60 minutes this problem will show up. 3. Seems to be tied into java or javascripts. If these are block, problem appears to stop. Actual Results: There is no step by step procedure that I've found that can cause this problem. The only thing that that I've done that appears to alleviate the problem is to use the java and javascript blocking feature in my ZoneAlarm Firewall product. I have noticed that this problem appears to occur at a faster rate when viewing streaming videos like from YouTube. Expected Results: When I incorporate Java and Javascript blocking on suspect webpages (usually ones that contain streaming videos) I get much less occurrence of this memory leak and shut down lock up. Of course those features that use the Javascript or Java do not work. I have noticed that many banner type ads are blocked when I do this and I wonder if the Javascript they are using is causing this. I am becoming more and more suspicious that some kind of Javascript that is being used in banner ads and streaming video is at the heart of this memory leakage and thus preventing FF from shutting down. Almost like FF is being hacked into via Javascript and being controlled externally. And as I said, I have been seeing this problem in every version that has come out since version 2.
Note that Firefox uses a garbage control system for JavaScript, which is pretty good (since Firefox 3 it now knows how to deal with circular references etc ...). I doubt that there's still many memory leaks in that area, although it's still possible. Most similar reports seem to be due to various plugins, like Flash. That's used for the streaming video that you claim that is related to the leak (like Youtube), not Javascript itself; Note that you have to update these plugins too (Firefox can't do it for you !), Flash 10 is for instance a lot better than previous versions. Java is a string candidate too, especially because it doesn't get unloaded from memory. We really need examples of the websites where you see this, otherwise this bug will be closed as an incomplete one. How else can this be fixed ?
Summary: Run away memory usage and unable to fully shut down Firefox → Firefox 3.0.10 Run away memory usage and unable to fully shut down Firefox
bug 467939 is very similar, can you please go to that bug from now on? I am marking this a dupe of it and reopening that bug so you can post more info.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Whoops, maybe the other way around. Sorry for the spam, just one more. Please post all info on this bug.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
What results using safe mode? http://kb.mozillazine.org/Safe_mode Better with beta and newer java 1.6_0_12 or 13? http://www.mozilla.com/en-US/firefox/all-beta.html the updated java will probably help Robert's issue
Email sent to Tyler Downer with latest information.
Posting Don's e-mail to me "Just got your message regarding your response to my bug report. Sorry to take so long to respond. For some reason your email didn't show up when it should have. As for your suggestions, they have been taken care of already with no change in status. Also note that since my report of the bug, Firefox has crashed on me several times. At this time, I can not put my figure on a specific action that is causing this. My programming experience goes back to the DOS and CPM days and I'm not up to speed on Windows or other GUI programming techniques or data. Perhaps you can provide me with a specific method to check out FF3 that can help to pin point what is happening. All I know at this point is what I've reported. Because I do a lot of research and blogging on a few sites including Weather Underground weather service whom I have been a member with for several years, it's difficult to lock into a specific cause other than the memory leak is connected with Firefox running for long periods of time and the memory usage continues to increase from it's initial startup value until Firefox begins to misbehave. In every case when this has happened, Firefox stays in memory even after being shut down. This prevents me from starting Firefox again unless I manually remove it using the Task Manager or restarting Windows. Because many of the blogs that I access link to other blogs and websites, it's very difficult to specify which websites might be causing this. I did have a problem with my own blog at WordPress recently where I couldn't insert pictures into my blog with out Firefox crashing. I've been told by WordPress that the problem with associate with a computability issue with Google Gears and WordPress. They claim that the problem has been fixed, but I haven't been out there to verify this yet. This issue did make me wonder if the memory leak issue could be connected with any other computability issues with other software running on my computer. I am running XP Home Edition with SP3 installed as well as IE8 and it's accelerators. I've done a registry scan and repair a while back and further registry scans haven't shown any further problems. I have all the latest recommend Microsoft Updates installed. The only other thing is I am running ZoneAlarm Extreme Security Firewall Software with there ForceField product turned on. The only problem I've noted with that is that I have to turn ForceField off when doing upgrades to Firefox. Any suggestions you can offer would be greatly appreciated. I've been fighting this memory leak issue for a long time trying to figure out what is going on. It was only recently I even found out what to call the problem. Several other Weather Underground members have brought up this same issue."
Don, you seem to be having a bunch of issues. The wordpress one is Bug 495286, but other than that, too little info to tell. Java update 14 has just been launched, with a bunch of fixes, so maybe try that. You say you have tried with a brand new, untouched profile? Make sure nothing has been changed or added (like extensions). Maybe support would be a better place for you to start at, then come back if they can not help you, unless wayne has anything he sees. http://support.mozilla.com/
Don, do you have any replies? Please make sure to upgrade to firefox 3.5 or later as well.
Severity: critical → major
Version: unspecified → 3.0 Branch
No reply, INCO. Please reopen if this still happens in Firefox 3.5.1 or later in Firefox Safe Mode or a new Profile. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Profiles
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.