Closed
Bug 149607
Opened 22 years ago
Closed 22 years ago
Mozilla does not free memory
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 131456
People
(Reporter: mozilla, Assigned: jag+mozilla)
References
Details
This might or might not be related to TAB-Browsing.
When opening several pages with tab browsing, the memory usage increases with the
number of pages and its memory load (as expected0).
However, closing the tabs does not frees used memory.
Worse, the memory load from about 20 tabs to 1 tab increased from 49MB to 58MB
of RSS.
At first I thought that mozilla acted as perl that does not frees memory to
be able to quickly reuse it.
However, opening new pages increased the memory usage, which means that
the memory is not being reused.
This might even be a slow memory leak behaviour.
Updated•22 years ago
|
Summary: Mozilla does not frees memory → Mozilla does not free memory
Comment 1•22 years ago
|
||
->INVALID ?
RSS indicates how many pages are currently in memory for Mozilla,
not Mozilla's working set and certainly not something as nebulous
as Mozilla's "memory usage".
Comment 2•22 years ago
|
||
*** Bug 146451 has been marked as a duplicate of this bug. ***
Comment 3•22 years ago
|
||
Build ID: 2002082606 (1.0.1)
This happens on W2k too. IMHO, OS ->All.
1. Open mozilla
2. Open some tabs with any pages
3. See memory usage in Task Manager
4. Close all tabs
5. See memory usage again (the same number)
May be some hidden pref should be implemented to free memory used after closing tab?
P.S. Reporter, please provide build ID with your bugs.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•22 years ago
|
||
Could this be a duplicate of 131456?
Please see my comment there.
Best regards,
-Chris
>Could this be a duplicate of 131456?
It seems so.
>Please see my comment there.
The only thing I couldn't test was the memory reclaim on certain cases.
Other than that is seems to be the same bug.
Comment 6•22 years ago
|
||
Based on Comment #4 and Comment #5, I'm marking this as a dup of Bug #131456. If
anyone disagrees, please reopen, and explain why you think it isn't a dup.
*** This bug has been marked as a duplicate of 131456 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•