Then close tab memory not deallocated

RESOLVED INCOMPLETE

Status

()

Firefox
Tabbed Browser
RESOLVED INCOMPLETE
13 years ago
11 years ago

People

(Reporter: Andrew Ivantsov, Unassigned)

Tracking

1.5.0.x Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 06/27)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

bug 131456 not closed. In 1.4.1 I see it. Then FF started - it use 20M. Then I open and close ~10 tabs (with browser.cache.memory.enable=false) it use~50M.

Reproducible: Always

Steps to Reproduce:
1.Then FF started - it use 20M. 
2.Then I open and close ~10 tabs 
Actual Results:  
(with browser.cache.memory.enable=false) it use~50M.


Expected Results:  
It must use 20M (may be +10%)

Comment 1

13 years ago
Exactly the same problem with browser.cache.memory.enable = false for FF 1.0.*, 1.5.*, Seamonkey.

Browser: Firefox 1.0.*, Firefox 1.5.*, Seamonkey

OS: Linux 2.4.*, 2.6.*
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
-> Closing as incomplete because of missing feedback if this is still reproducible in the latest release (Firefox 2.0.0.4) or Trunk Build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE

Comment 4

11 years ago
See the discussion in #130157
You need to log in before you can comment on or make changes to this bug.