Closed
Bug 370203
Opened 18 years ago
Closed 18 years ago
memory leak when Thunderbird runs for long time
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 370202
People
(Reporter: jon, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: version 1.5.0.9 (20061207) If I run ThunderBird for 24 hours, note the used system memory, quite ThunderBird, and then return to ThunderBird, I can often regain between 100 and 200 MB of RAM. ThunderBird is using more and more memory as it runs Reproducible: Always Steps to Reproduce: start FireFox. Use it for 24 hours. Note system memory usage using TaskManager. Quite FireFox. Restart FireFox. Note system memory usage has declined by at least 100 MB Actual Results: over 100 MB of memory is reclaimed Expected Results: memory usage should not change
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Comment 2•17 years ago
|
||
Jon, did you see this problem with both FF and thunderbird?
Wayne: yes, I see it with both FF and TB. Last time I complained, I was told not to use Flash plug-ins. I've given up on this getting resolved.
Comment 4•17 years ago
|
||
Jon, Some possibilities for you to try, and then report results in this bug : - if you need TB 1.5, upgrade to TB 1.5.0.13 which fixes bug 387403 - turn off GDS (google desktop search) if you installed it - reduce number of RSS automatic checks for new articles (bump to high value) - delete <foldername>.msf files with thunderbird shut down, and restart (some of the above are from bug 346361) if the above don't help, start in _safe mode_, with v2 or executable/rpm from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/ and determine if same results
Summary: memory leak when run for long time → memory leak when Thunderbird runs for long time
Version: unspecified → 1.5
You need to log in
before you can comment on or make changes to this bug.
Description
•