Bug 85916 – mozilla memory leak

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 85916 - mozilla memory leak

Summary:	mozilla memory leak

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	mozilla (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Christopher Blizzard
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-03-10 14:53 EST by Gene Czarcinski
Modified:	2007-04-18 12:51 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-10-27 14:25:44 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gene Czarcinski 2003-03-10 14:53:13 EST

Description of problem:
This is related to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83942

I have gotten my original report against galeon to also occur with mozilla.

There appears to be a memory leak of some sort when the mozilla process stays up
for a long time.  The memory usage grows over time (shown by the
gnome-system-monitor) starting with about 25MB and growing.  It still works OK
with about 45MB but becomes unusable when it had grown to 60MB.

Clearing the memory cache (set to 4096MB) has no effect.

Version-Release number of selected component (if applicable):
8.0.95+rawhide, mozilla 1.2.1-22

How reproducible:
yes

Comment 1 Gene Czarcinski 2003-03-11 02:28:57 EST

Memory usage seems to grow even when minimized and left idle.  At some point
>60MB it seems to choak and become unusable.

Comment 2 Gene Czarcinski 2003-03-13 11:37:59 EST

This probably shoyuld be reported upstream to http://bugzilla.mozilla.org

However, looking over their reporting it is not clear to me just what
package/component or version to report this under.  Any tips?

Comment 3 Gene Czarcinski 2003-03-13 16:13:16 EST

Oh, this is going be fun (NOT) ...

I figured out how to file a bugzilla report for mozilla
http://bugzilla.mozilla.org/show_bug.cgi?id=197224

Unfortunately, I soon got the following:

------- Additional Comments From wolruf@free.fr  2003-03-13 11:24 -------
This is a known issue, Mozilla developers need some help on very precise steps
on how to reproduce the issue using latest build (1.2.1 is too old).
Unless you do so, this bug report will remain untouched or be marked INVALID.


I am not sure how to proceed from here.  This is not very helpful and I am not
that motivated to dig into this.  If I was, I would get the source code and do
some "instrumentation" or something.  In fact, it may be easier to just kill the
process off every so often and restart it.

To me, I would think that this was serious enough that there would be interest
in fixing it.  I find it had to believe that I am the only one see this.

Comment 4 Gene Czarcinski 2003-10-27 14:25:44 EST

OBE

Note You need to log in before you can comment on or make changes to this bug.