Status

SeaMonkey
General
--
critical
RESOLVED INVALID
15 years ago
14 years ago

People

(Reporter: Tom Meinlschmidt, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

after a few days with Firebird running I accindentaly run Task Manager and
Firebird was using about 80megs of memory. After closing (or killing from
tasks), reloading with the same tabs it takes about 30megs, but periodically
increasing used memory. Tab closing has no effect. With huge amount of used
memory it slowdowns its responses, and became unusable.

Reproducible: Always

Steps to Reproduce:
1.load firebird and taskmanager
2.open some tabs, do some refreshes
3.try to close and reopen abs

Actual Results:  
consumes more and more memory

Expected Results:  
free allocated memory :)

Comment 1

15 years ago

*** This bug has been marked as a duplicate of 81446 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → DUPLICATE
I don't think this bug should be marked as a duplicate.  We don't want all
memory leaks marked as duplicates of a single bug report, just like we don't
want all layout bugs marked as duplicates of a single bug report.  I also
wouldn't be surprised if there are some Firebird-specific leaks.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

Comment 3

15 years ago
I have noticed this problem in both Firebird and Mozilla 1.2-1.4 on Windows 98
and Windows ME.  I open and close tabs in the browser and eventually get "Low
Resources" messages from Windows.  The workaround is to close and reopen the
browser.  

To me, it sounds similar to bug 213534 on Mac OSX.

Updated

15 years ago
QA Contact: asa

Comment 4

15 years ago
taking over qa abandoned bugs.
QA Contact: bugzilla

Comment 5

15 years ago
.
Assignee: blake → general
Component: General → Browser-General
Product: Firebird → Browser
QA Contact: bugzilla → general
Version: unspecified → Trunk

Comment 6

15 years ago
I have the same problem with this version under Win2000 and XP:

Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.5) Gecko/20031007

Core bug(s) ?

Comment 7

15 years ago
I can reproduce this bug on both Mozilla 2003123008 and the latest Firebird .8
nightly build Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b)
Gecko/20031230
x86 Windows 2000
Below are the memory usage reports from Windows Task Manager:

Mozilla 2003123008:
Freshly opened 10864 (1 tab open)
Open 3 tabs, open any site in each, refresh. 18954
Close 3 newly opened tabs 18728
Open 3 tabs, open any site, refresh. 22008
Wait a while 11360
Close 3 newly opened tabs 17016
Open 3 tabs, open any site, refresh. 19080
Close 3 newly opened tabs 19176

Firebird 8:
Firebird 20031216: 33744 on start (3 tabs)
Open 3 tabs, open any site, refresh. 37544
Closed 3 newly opened tabs, 36756
Open 3 tabs, open any site, refresh. 37096
Close 3 newly opened tabs 36380
Open 3 tabs, open any site, refresh. 40660
Close 3 newly opened tabs 38376
etc
 after a few iterations of this, closed all tabs except for one open site. 52608

Comment 8

15 years ago
Maybe what you observe is the filling of the cache.
How big is the memory cache? (Enter about:cache in the location bar)
Is Mozilla/Firebird still leaking if the cache is full?

How much memory is used (task manager) after you cleared the (memory) cache?

Comment 9

15 years ago
Reporter, do you see this in a recent build?
If yes, could you post the URLs to verify.

This could be also a dup of bug 213391.

Comment 10

15 years ago
Without actual memory profiling, this bug isn't of any real value. Please reopen
if you can point to a specific demonstrable leak.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago15 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.