Closed Bug 197356 Opened 21 years ago Closed 21 years ago

memory cleanup / garbage collection does not release memory, when tab is closed

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 131456

People

(Reporter: cs, Assigned: jag+mozilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

I guess "tabbed browsing" was, among other reasons, added to enhance performance
and save on memory.
Now I use tabbed browsing quite extensively and find that it saves a lot of
memory AS LONG AS YOU DO NOT CLOSE ANY TABS.
I regularly open 3 tabs which I keep open permanently. With these tabs open the
mozilla.exe process consumes about 27, never more than 28 MB of memory.
Now I open a web connection to an IBM Director which uses Java.
Memory usage of mozilla.exe goes up to 58 MB. No problem while the page is open.
After closing the tab again (and manually unloading Java Runtime) the usage of
mozilla.exe does not go back down again. I checked regularly for about half an
hour and the memory usage was still around 57 MB, which I think is not acceptable.

Reproducible: Always

Steps to Reproduce:
1. Start Mozilla Browser
2. Start XP Task Manager and watch mozilla.exe mem usage
3. Do memory intensive task in a new tab (like working on pages with java)
4. Watch mem usage of mozilla.exe again (will bei higher)
5. Close memory intensive tab
6. Watch mem usage of mozilla.exe again to see it has not substantially decreased.

Actual Results:  
The mem usage of mozilla.exe was still as high as with the memory intensive tab
open.

Expected Results:  
Release the memory of the closed memory intensive tab.
Whiteboard: DUPEME

*** This bug has been marked as a duplicate of 131456 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Core → SeaMonkey
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.