Closed Bug 89938 Opened 24 years ago Closed 24 years ago

Memory Leaks, mozilla!!!

Categories

(Core :: XPCOM, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: dragonflowtest, Assigned: kandrot)

References

()

Details

(Keywords: memory-leak)

step 1: record the memory statistic before running the mozilla-0.9.2 step 2: navigate http://www.hotmail.com/ step 3: log in my mail box step 4: log out my mail box step 5: exit mozilla-0.9.2 step 6: record the memory statistic after exitting the mozilla-0.9.2 step 7: differentiate the two statisic, about 1M Memory Leaks!
We are aware that we have memory leaks in Mozilla, but without a log of *where* the leaks are happening - this is not useful. Besides, this is in the wrong component. XPCOM is not to blame for faulty usage. :) Voting for INVALID until we get some useful information.
Keywords: mlk
Erm. Memory that's not deallocated upon application exit is _not_ the application's memory leak. A memory leak is memory that the application allocates and loses pointers to so it can't deallocate the memory. If the memory is not deallocated upon application exit, that's a bug and/or memory leak in the operating system kernel.
I second the vote for INVALID, and marking it as such.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.