Closed Bug 410157 Opened 18 years ago Closed 18 years ago

massive memory leak

Categories

(Firefox :: Shell Integration, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: doekia, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Firefox exhibit massive memory leak in this version. Reproducible: Always Steps to Reproduce: plugin/extensions: DOM inspector 1.8.1.11, Talkback 2.0.0.11 cache.disk.capacity = 32768 cache.memory.capacity = 4096 browser.sessionhistory.max_total_viewers = -1 1. Start Firefox -> memory usage 25M, vm size 25M 2. (startup page is http://fr.start2.mozilla.com/firefox?client=firefox-a&rls=org.mozilla:fr:official ) 3. hit the google image search and serach for "memory", move the the next page of result. 4. menu: ?/About, hit Contributors, wait for the markee to scroll then close the popup 5. move the next page of result into the google page 6. menu: Tools/DOM Inspector 7. expand the BODY tagin the tree, select the last CENTER tag 8. scroll up to the body element using keypad up-arrow 9. close DOM inspector 10. return the the startup page 11. Clear all cache (Shift+Ctrl+DEL) Actual Results: !! Memory usage: 36MB, VM size: 43MB Expected Results: 25MB ich
This forces me to re-start Firefox every 1/2 hour based on my hardware constraints (320MB of RAM)
Version: unspecified → 2.0 Branch
There is nothing here to suggest a real problem except misunderstandings about memory management. In the future try reading http://plugindoc.mozdev.org/faqs/memusage.html and http://developer.mozilla.org/en/docs/Bug_writing_guidelines and http://dbaron.org/log/2006-01#e20060110a before filing such bugs.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Version: 2.0 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.