Closed Bug 403066 Opened 17 years ago Closed 17 years ago

memory leak if thunderbird is left on overnight

Categories

(Thunderbird :: General, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: cheatcountry, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b1) Gecko/2007110703 Firefox/3.0b1 Build Identifier: version 2.0.0.10pre (20071108) I had thunderbird on for about 48 hours and when I woke up it was using 400mb of memory Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: it should have only used up around 50mb of memory
To Franklin Moormann(bug opener): What is evidence of "memory leak" and "memory leak by Tb's flaw"? What is grounds of your of "memory leak" and "memory leak by Tb's flaw"? Please note that next; 1. If memory leak occurs, virtual memory allocated to an application always increases on each "memory leak". 2. But "'larger memory size than your expectation' only" (which do you mean by your "memory size"? virtual? real? Or both?) can not be an evidence of "memory leak by an application", even though real "memory leak" is suspected when "larger memory size". Please note that here is bugzilla.mozilla.org, here is not support forum nor customer help center. Please read thru all of; A) Meta Bug 329015 B) Bugs listed in dependency tree for meta Bug 329015, including closed bugs C) Bugs or articles/documents/Web pages pointed by all of A) and B) before shouting "memory leak of Tb!", please, please. Question again. What is the evidence of "memory leak by Tb's flaw"? Please note that I never say "no memory leak of Tb/Fx/Seamonkey". I already know that Mozilla famliy has many real "memory leak" problems. I'm simply saying that "Tb eats up my memory" at bugzilla.mozilla.org won't solve any problem.
Oh sorry, it was meta Bug 320915, instead of Bug 329015. Sorry for spam.
no response, perhaps franklin is gone. => incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.