1.  Limit the amount of physical or locked-in memory Firefox is demanding.
2.  Enforce memory quotas on plugins and add-ons.
3.  In the Addon-s page, report Current Memory and Resource usage against all addons, themes, plugins, etc.  That way I'll know what pluging to delete instead of needing to delete all of them
4. Provide options to report  Current Memory and Resource usage against all open Tabs and web pages.
5. Make memory quotas (min and max) user settings.
6. Pass on the word among developers that using more memory is NOT a way to make things faster.  Once too much memory is being used it just stops the rest of my PC from running efficiently and we are Still slow in other areas.
7. May be firefox needs to provide it's own memory management for Javascript and plugins.
8.   Provide some external monitor that can do better memory clean-up.

I've seen many posts on this very subject, this one is from as far back as Seven(7) Months ago: * https://support.mozilla.org/en-US/questions/1011071 My own example is from just yesterday. ON Windows 7 64-Bit, 64-Bit Firefox, with 16 Tabs open, Firefox was using over 1.3GB of physical memory (from the 4GB in the machine). This example documents up to 2GB of memory with Windows 8 * https://support.mozilla.org/en-US/questions/1059235 And the first guy had 2.4GB swallowed up (back in January or so). There are other examples on that same article; but we can't report "I have this problem too" because the thread is now locked. In my case the problem is Firefox playing vampire to PHYSICAL memory. Chrome had 16 Tabs open yesterday and was only taking up about 200MB of Physical memory, the working set for ALL tabs (I added them up manually) was around 800MB. This is a work machine. I need to run compilers and VirtualBox appliances, it is not a web browsing machine. The memory foot print for an accessory like a browser should be under half a gigabyte imho. If an special page or an app needs more, there should be some kind of process or mechanism to "enable" this that can be checked off by the user. As it stands, I cannot work and use firefox at the same time. While I might prefer the Firefox experience, I will need to swap to a different browser until the memory problem is resolved. It is simply not enough to 'blame' plugins or say get more memory. There needs to be better solutions. Some suggestions . Firefox should and could do most of them 1. Limit the amount of physical or locked-in memory Firefox is demanding. 2. Enforce memory quotas on plugins and add-ons. 3. In the Addon-s page, report Current Memory and Resource usage against all addons, themes, plugins, etc. That way I'll know what pluging to delete instead of needing to delete all of them 4. Provide options to report Current Memory and Resource usage against all open Tabs and web pages. 5. Make memory quotas (min and max) user settings. 6. Pass on the word among developers that using more memory is NOT a way to make things faster. Once too much memory is being used it just stops the rest of my PC from running efficiently and we are Still slow in other areas. 7. May be firefox needs to provide it's own memory management for Javascript and plugins. 8. Provide some external monitor that can do better memory clean-up. Given the stark comparison between resource consumption between Chrome and Firefox in my experiments yesterday, I think firefox needs to reassess some design choices in it's memory allocation and architecture. The results I've seen put me in mind of early Java/VM memory usages and the issues will be extremely similar. There may be lessons to be learned from that part or computing history. I'm happen to try actual solutions but we need practical steps. Getting my boss to double my memory when all that seems to do is double the memory-plate size firefox eats is not really as practical as it might seem sitting at your desk with 16GB or ram in a developer desktop. cheers ....