Originally Posted by kevindd992002
Ok. I want to do it manually though
Regadring the 10Mb RAM usage when minimized, why doesn't it work for me as I've said?
There's actually two different settings to deal with. Here's a better description of config.trim_on_minimize:
On Windows operating systems, when a program is minimized and left for a period of time, Windows will swap memory the program is using from RAM onto the hard disk in anticipation that other programs might need RAM. Because of the way Mozilla applications are stored in memory, Windows is much more aggressive in swapping out the memory they use, which can cause a delay when the program is restored. This preference determines whether to allow Windows to swap out memory from a minimized Mozilla application.
When setting this to 'True', you'll be able to reduce the amount of RAM used but it may not be right away. When you minimize Firefox or leave it running without messing with it, Windows will swap out the memory Firefox is using. Windows overall controls everything but this setting allows the memory being used by Firefox to be swapped out when the above conditions exist.
browser.sessionhistory.max_total_viewer should have an 's' at the end. So the correct command/setting should be browser.sessionhistory.max_total_viewers Here's a better description for the setting:
browser.sessionhistory.max_total_viewers [Integer] - This option determines how many pages to store in memory to speed up the back and forward buttons in Firefox. The default of -1 automatically determines the amount based on your system RAM, and is generally recommended. At 512MB of RAM, 5 pages are held in memory, while 1GB or more of RAM holds 8 pages. You can set this value to 0 to hold no pages in RAM (only recommended for very low RAM or troubleshooting purposes), or increase the value if you often use the back and forward functions for more than 8 pages.
So these two settings will control the amount of ram used by Firefox/Waterfox. I recommended changing the browser.sessionhistory.max_total_viewers from '0' (Do not store any pages in memory.) to '-1' (Automatically determine the maximum amount of pages to store in memory based on the total amount of RAM (Default)). You'll use more memory with this setting but it may solve the jittering in YouTube videos by caching/buffering the video into memory while streaming it. You can also use positive integers to control the amount of RAM used. Take a look at the following page for additional info: