How to Keep Firefox From Using Too Much Memory

Or similar Browsers, Palemoon, Waterfox, Comet Bird, etc.

Version 2.0

When you browse the web for long periods of time without restarting Firefox, or

launching a fresh instance of the browser, the memory usage can go through the

roof, bringing Firefox to a crawl. This is not specifically a Firefox problem. It can

affect all browsers including Chrome and Opera. To prevent this, it is

recommended to periodically restart the browser before memory usage becomes

too high. There is even a handy add-on that lets you automatically restart your

browser keeping all open tabs intact, called Memory Restart. But you can avoid

having to restart if you adhere to the following best Practices.

Go easy on extensions

Keep the number of add-ons installed to a minimum. Periodically review the add-

ons you have installed, say every 3 month or every month, depending on how

frequently you install new extensions. Justify the presence of each extension and

remove anything that you haven't used in a while, or those whose usefulness is over.

Prune down the list as much as possible!

Don’t forget plug-ins

Firefox displays add-ons and plug-ins on two separate pages. While you are

reviewing your list of add-ons, don’t forget to check out the plug-ins page. If you

have never opened this page before, you might be on for a surprise.

Dozens of plug-ins, many of which you have never installed on purpose. Click the disable button next to each of these plug-ins. Don’t give a second thought. You don’t need all of them! If you use browser only for KoC , you don’t need Silverlight for example!

About:config about:config is a feature of Mozilla applications which lists application settings

(known as preferences) that are read from the profile files prefs.js and user.js, and

from application defaults. Many of these preferences are not present in the

Options or Preferences dialog. Using about:config is one of several methods of

modifying preferences and adding other "hidden" ones.

In Firefox and similar, type about:config in the Location Bar (address bar) and

press Enter to display the list of preferences. If you see a page with the warning

message, This might void your warranty! click the button labeled "I'll be careful, I

promise!", to continue (in fact, there is no warranty whatsoever, it's more a joke

to ensure that users are aware of what they are about to do). Use the checkbox

there to avoid the warning in the future.

After clicking “ I’ll be careful, I promise” you get a page like this.

Search Box, you will need it in

a bit.

Reduce memory cache

When you open a webpage with images, Firefox stores the images for a time in uncompressed

form. This results in an improvement in speed at the expense of greater memory use. If too

many large, uncompressed images are in memory simultaneously, it can lead to increased

memory use. Web sites with a lot of large images can require very large amounts of memory.

This problem can be mitigated by putting a cap to the amount of memory used by decoded

images.

To do so, open the about:config page and search for:

image.mem.max_decoded_image_kb

By default, this is set to a very high value – 256000 or ~256 MB. Reduce this cache to

something smaller, such as 50MB.

Double click on the line and you get a pop up!

Change to 51200 (50 MB)

Click OK.

Your new line looks like this now with the NEW value.

Kingdoms Of Camelot is full of pictures, small & big and that is why we are

adjusting this line and the memory that is standard assigned to this.

Similarly, memory assigned to Javascript is way too high.

In webpages where there are lots of scripts doing lots of fancy things, (PowerBot+ & TCO)

memory footprint can increase quickly. To reduce memory consumption by Javascript, locate

the parameter:

javascript.options.mem.max

and change its value from -1 (automatic) to 51200 (50 MB).

( Same procedure as before, double click the line, you get pop-up. Change value in Pop-up from -1 to 51200

and click OK)

Also find :

javascript.options.mem.high_water_mark

and set it to 30 from the default 128.

( Same procedure as before, double click the line, you get pop-up. Change value in Pop-up from 128 to 30 and

click OK)

This parameter tells the garbage collector to start running when Javascript is using 30 MB of

memory. Garbage collection releases memory back to the system. And this is how we help all

scripts, including PowerBot+ & TCO to release their memory back into your PC

Feel free to experiment with other values. Your needs may vary. These are Safe Values.

Reduce session history

Firefox caches each tab you have open in such a way that they don't have to be re-parsed when

you use the back and forward buttons to flip through history. This cache is different from the

memory cache. The default is set to 50, meaning Firefox will remember the last 50 pages

opened by each tab. If you have the habit of reusing tabs (as opposed to opening new tabs), the

browser session history can grow to fantastic sizes.

So what you should do? Close the tab when you are done with a page and open a fresh tab for a

new page. Alternatively, you can reduce the number of pages Firefox keeps in cache.

To do this, open about:config and set the desired value in :

browser.sessionhistory.max_entries

A value of 10 should do.

( Same procedure as before, double click the line, you get pop-up. Change value in Pop-up from 50 to 10 and

click OK)

Enable pipelining Browsers are normally very polite, sending a request to a server then waiting for a

response before continuing.

Pipelining is a more aggressive technique that lets them send multiple requests before

any responses are received, often reducing page download times.

Here you need to search for the below-mentioned entries and change their status to what is

mentioned below:

network.http.pipelining -> true

network.http.pipelining.aggressive -> true

Network.http.pipelining.maxrequests -> 8

Network.http.pipelining.ssl -> true

To quickly find all of these options, type network.http.pipelining

Enable HTTP pipelining behind a proxy If the network you are connected to is located behind a proxy of some sort, you’ll need to do an

additional step for this to work. Inside the about:config window, search

for network.http.proxy.pipelining .

Set from False to True

IF for whatever reason you have problems after these edits, you can simply revert

by reverting the above steps. And restore the Original Values.

You are Done , you can now close the browser completely, then restart it and go back to Game.

Sharing is knowledge, and a lot of players are not sharing. Yes, it gives you and edge, or advantage, but

it leaves also many people clueless. The objective of these tutorials, is to teach, learn, educate players so ALL players have

a better under understanding of the game. The more players participate, the better the overall experience is for all players.

More attacking and defending means “lively” domains full of activity.

http://www.slideshare.net/Aderik/documents