Closed Bug 139447 Opened 22 years ago Closed 22 years ago

bad memoryleak (1Mbyte/s) visiting bugzilla pages

Categories

(SeaMonkey :: General, defect)

x86
Windows NT
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 120712

People

(Reporter: harm.verhagen+bugzilla, Assigned: Matti)

References

()

Details

(Keywords: memory-leak)

Attachments

(3 files)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0rc1) Gecko/20020417
BuildID:    2002041711  (v1.0 RC.1)

Following the URL (bugzilla query) mozilla starts to eat memory as soon as the
query is finished. It consumes memory at a rate of +/- 1Mbyte/second.
Interesting to see is that if you hit back the memory leaking stops.



Reproducible: Always
Steps to Reproduce:
1. click url
2. open taskmanager
3. wait till url (bugzilla query completed)

Actual Results:  mozilla memory consumption increases with a rate of about 1
Mbyte/second as soon as query is completed. 
Starting at about 17Mbyte memory use, I killed it when it got to 130Mbyte memory
use (see atachment)
attachement (memhog.bmp)
Reproduced the problem. Only, this time it took up 306 mb!. Attached are: a
snapshot of task manager and the html source of the bugzilla output for the url.
the time right now is 23/04/02 8:00 am pst. Mozilla rc1 on win2k sp2.
I am attaching the text of the bugzilla output screen. This is not the html
source. I tried to open the window. It pegged cpu to 100% for a long time.
Anyway, the idea is to demonstrate that the it does not require 306 mb of vm.
I have closed the bugzilla output window. But the memory has not been returned,
it fell from 306 mbn to 281 mb.
how many bugs does that query return?

I suspect this is a dup of the "showing a large bugzilla query takes lots of
ram" bug.
Whiteboard: DUPEME
Keywords: mlk
What bug# are you refering to ?
the query returns about 3000 bugs, taking up about 270 kilobyte in text.
Note: after that when browsing to other pages, the memory (hundreds of
megabytes) is _not_ reclaimed.
Bug 120712 is it.

*** This bug has been marked as a duplicate of 120712 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
reporter: indeed, is a dup
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: