Browser.cache.memory.enable

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is browser.cache.memory.enable.

This article describes the preference browser.cache.memory.enable. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

1 Background 2 Possible values and their effects

2.1 true 2.2 false

3 Caveats 4 Recommended settings 5 First checked in 6 Has an effect in 7 Related bugs 8 Related preferences

[edit]

Background

When a page is loaded, it can be cached so it doesn't need to be rerendered to be redisplayed. This preference controls whether to use memory to cache decoded images, chrome (application user interface elements), and secure (https) pages. browser.cache.memory.capacity controls the maximum amount of memory to use.

[edit]

Possible values and their effects

[edit]

true

Allow decoded images, chrome, and secure pages to be cached in memory. (Default)

[edit]

false

Don't cache decoded images, chrome, and secure pages in memory.

[edit]

Caveats

Setting this preference to false causes less memory to be used but also increases the load time of previously visited pages and dialogs, especially those of secure sites. If browser.cache.disk_cache_ssl is set to true, secure pages will be stored in disk cache, not memory cache.

[edit]

Recommended settings

Users who are having problems with memory consumption can try setting the value to false to lower memory consumption. Users who have no problems with memory should leave it at true.

[edit]

First checked in

2001-06-27 by Darin Fisher

[edit]

Has an effect in

Netscape (all versions since 6.1) Mozilla Suite (all versions since 0.9.1) Phoenix (all versions) Firebird (all versions) Firefox (all versions) Thunderbird (all versions) Minimo (all versions) SeaMonkey (all versions)

[edit]