Closed Bug 256139 Opened 18 years ago Closed 18 years ago
memory cache exceeds limit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040621 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040621 When using mozilla for a few days heavily without restarts, the memory usage goes way high. When looking at url about:cache this is displayed: Memory cache device Number of entries: 607 Maximum storage size: 21504 KiB Storage in use: 36052 KiB Inactive storage: 0 KiB Also, mozilla in top shows very big memory usage. Right now I have 108M of ram in resident memory and 146M of virtual size. Reproducible: Always Steps to Reproduce: 1. Well, try using mozilla for 3 days heavily 2. 3. Expected Results: I would excpect that mozilla would not go past it's memory cache size.
What web pages are open at the time you check the memory cache? If you currently have a page that has x amount of image data, mozilla's memory cache usage will be at least x, even if that number is higher than your setting for the max. (Otherwise, it wouldn't display the entire page)
There aren't much web pages open but there are few.I am doing web development so I have to reload existing pages over and over again. Usually I have project calendar page, development site, a php.net and a few more. From time to time I go surf around but after surfing I close those tabs. In middle next week, when I'm back at work, I'll get back to you on exact number of pages and more info.
Okei, the good part is that I can't reproduce it any more. I upgraded my mozilla from 1.7 to 1.7.2 and compiled glibc with nptl support and that seems like has fixed the problem ... maybe. Well, mozilla now crashes from time to time, so I am not able to run it for so long any more. Sry to have bothered you all. I'll try to get more info on the crashes and report that as a separate bug.
*** This bug has been marked as a duplicate of 213391 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
QA Contact: networking.cache → benc
You need to log in before you can comment on or make changes to this bug.