This is a problem reported in another long thread and the thousands viewing that indicate it is a major concern, and continues in Firefox 23 not just the Firefox 20 from the report.
Original thread title: Version 20, Memory Leak Still? Original thread Link https://support.mozilla.org/en-US/questions/958108
I am one of the forum moderators, and do not have this problem myself. Unfortunately I do not even have a Mac.
I am trying to make information easily findable. I have started this thread with two aims
In this Thread
PLEASE NOTE, because I am trying to keep this as a tracking and cross linking thread I am reserving the right to heavily edit or delete any post in this thread as I see fit.
I am intending mainly to keep content in separate threads with only summary, extracts and links in this thread. Feel free to post in this thread with definite solutions or to mention any thread you consider relates to this problem.
This thread is NOT going to deal with any issues involving Flash Player.
Knowledge Bases etc
Your Operating System
Note Firefox Knowledge base articles should display information related toyour own OS with an option to view other versions of the article. Mozillazine articles usually cover all OS within one article.
Topics Under Investigation The title of the topics may be subject tochange as investigation progresses.
(Noah or other mods feel free to edit this thread as required)
The primary issue is
If you see this issue on the any particular site and you have accessed the site with all plugins disabled, and preferably from a clean additional profile please start your own thread about the issue using /questions/new then post back here to confirm you have done that. We know of one particular site causing this problem, but it is pay for access, so identifying another site may be helpful, and will also indicate other sites are affected. Possibly this sort of problem will most likely be seen when accessing large databases.
Initially you need not worry about whether it is in fact heap-unclassified. If you get any large and rapid increase in memory usage of that sort of order (2-3 GB RAM in 10 minutes) something is seriously wrong and we will be interested.
As a secondary issue if you get similar problems but with only a single add-on enabled please also start a new thread then post back here. We may also be interested in other cases where memory usage is going over 2-3 GB even if not that rapidly.
These are the suggested steps for those wishing to demonstrate this problem, from
Visit about:memory as soon as you open Firefox and before you begin any browsing. Then, copy and paste everything on the page to http://pastebin.com and return to this site and give us the url to the pastebin.
Then grab another copy of the about:memory data during the halfway point of 10 minutes. Or when you notice you've reached the halfway point of the memory leak (if the highest you've seen is 2GB for example, then get the about:memory @ 1GB).
And lastly, get one more copy of the about:memory data before Firefox becomes unresponsive but is near the 2GB (or whatever) high memory you speak of. This part will be tricky if Firefox is hanging. :/
So you should have about 3 pastebins worth of about:memory data when you're done and I will show that to the memory dev and report back on his findings.
It'd be nice if you could just paste that data here but the first part of it becomes mangled & unreadable due to how the "Main Process" data section is formatted. See my example attempt here: https://support.mozilla.org/en-US/questions/963890
Being the originator of the original post that has birthed this post, I would like to mention that this issue was originally brought up at version 4, and again at version 20.
That is the version 4 query.
That being said, I hope this finally can be resolved, because this seems to be a problem that has been ongoing for quite some time.
As Cyberpawz mentions above this was noticed in Firefox 4 then Firefox 20.
The entire Original Post from Cyberpawz relating to Firefox 20:
I've been using Firefox since well, lets just say long enough... Version 20 for the Mac seems to not have fixed any bugs or memory leaks.
One of the "fixes" is to restart Firefox, which is the only "fix" that works, but this really isn't a fix, this is a stopgap situation, in where you release the memory by closing it...
Are there other people with this same situation? My Firefox uses with nothing in the main page except google.com, if it's open for over 24 hours over 1GB of ram... 2 GB in 48 hours, etc...
The most Firefox has ever used was 5GB before I shut it down, now I know, restarting Firefox seems to stop this from happening, but as I said, this is a stopgap, there is something inside Firefox that makes this happen.
Is there anything in the future that will fix this issue, or is Firefox going to be forever a Memory Hog worse than Microsoft Office?
Noah posted in that thread Extra thought: If you have a large store of anything, I think that can contribute to the memory problem. For example, having 500+ bookmarks saved or 200 downloads saved in the download history or having 800+ cookies saved or having 100+ passwords saved and so on. You get the picture.
posted a general solution usually expected to resolve the issue
Cyberpawz was running Ghostery
at a time when it transpired that Ghostery caused a leak but apparently has continuing problems after updating that.
Other than on one particular site I am not yet aware of anyone able to reproduce this problem and willing to try in safe mode in a clean profile with all plugins disabled and then produce the about memory results that would help developers.
has kindly participated in filing a bug for this article,
but AFAIK that only has information and steps to reproduce and about:memory information in relation to the problem occurring on a single specific site.
I am not aware of the problem being demonstrated with data for other sites. (No doubt Noah or curmudgeon99 will correct me if that is wrong)
This is a thread by curmugeon99. It may contain useful general tips & links. But has no resolution for curmugeon99
This thread resulted in a bug being filed, and at the moment is the only thread I am aware of where Windows has similar problems.