Closed Bug 330406 Opened 18 years ago Closed 18 years ago

memory cache exceeds value set in browser.cache.memory.capacity

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Version:
1.5.0.x Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 213391

People

(Reporter: nul.all, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

As outlined by http://kb.mozillazine.org/Memory_Leak , browser.cache.memory.capacity was set to 4096; however, about:cache?device=memory currently shows the following:

Number of entries: 	1872
Maximum storage size: 	4096 KiB
Storage in use: 	102596 KiB
Inactive storage: 	0 KiB


Though the numbers change, this problem ("Storage in use" being much greater than "Maximum storage size") occurs frequently.
Please somebody fix this! I love Firefox (been using it since Phoenix 0.2) but if I can't get these memory hogging issues under control, I'm going to have to switch to Opera.

Reproducible: Always

Steps to Reproduce:
1. Set browser.cache.memory.capacity (in about:config) to 4096
2. Restart browser
3. Use for extended period of time with multiple tabs
4. Access about:cache?device=memory

Actual Results:  
Storage in use >> Maximum storage size

Expected Results:  
Storage in use = Maximum storage size

browser.cache.memory.enable=true

(sorry if this is a duplicate, i tried searching!)
Version: unspecified → 1.5.0.x Branch
Summary: memory cache largely exceeds value set in browser.cache.memory.capacity → memory cache exceeds value set in browser.cache.memory.capacity
This may be related to bfcache, does setting browser.sessionhistory.max_total_viewers to 0 help?
Severity: critical → normal
Mike,
I previously had max_total_viewers set to 3, but I have changed it to zero (goodbye sweet ultra-fast back and forward, I will miss you!) and I will report back to see how it affects things.
For the record, I am running on 512MB RAM
Related to/duplicate of Core bug 213391?
the current limit is not a hard limit - you can use more if you have a page with lots of images, or many tabs open, etc ...

*** This bug has been marked as a duplicate of 213391 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.