Closed
Bug 403632
Opened 18 years ago
Closed 18 years ago
each Thunderbird >= 1.5.1 eats up all available mem after a while
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: whitedog, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: each version since and including v1.5
Each newer (1.5++) Thunderbird tends to kill itself after a while because of a major mem-leak under w2k(sp4) - reproduceable after an hour it ate up to max mem available on the system (tested 5 different machines so far) incl. swap.
Still using v0.9 because since 1.? i encountered these probs and no version till then can be left open for more than half an hour... really annoying.
(kept checking for a year now on different machines but needed to downgrade each time so far)
Reproducible: Always
Steps to Reproduce:
1. open thunderbird
2. wait a while
3. after roughly half an hour it starts to leak
4. latest an hour later system reports beeing short of mem
5. latest one and a half hour later all sytem-mem is occupied
Actual Results:
install thunderbird v>=1.5, open it and wait.
my old versions (0.9-1.1) are perfect, no mem-leak, work great though.
did you compile since 1.5.1 with some new microsoft libraries??? :)
(ok, the speed the mem got eaten varies from version to version but never saw one of the newer versions which did not start to eat mem after half an hour under w2ksp4...)
causes dependent problems, anything you like what can happen if the system is totally low on mem and affects each other running sw...
Comment 1•18 years ago
|
||
Made sure it's not caused by an extension?
Other possibility: there is something strange with your profile - you could create a new one, and copy over the actual old mail folders to the new profile.
Comment 2•18 years ago
|
||
please comment if you see this problem with version 2.
do you have RSS feeds?
Whiteboard: closeme 2008-06-15
Version: unspecified → 1.5
Comment 3•18 years ago
|
||
RESO INCO per last comment or preceding one.
If you think this is in error, respond answering why.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2008-06-15
You need to log in
before you can comment on or make changes to this bug.
Description
•