47892 - loading page exponentially increase memory use

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect, P3)

Description

[Dave]

While loading the above page, mozilla's memory useage according to top increases
from the regular ~10-14 to well above 20.

I'm using build 2000080704/Linux

Also tested on Netscape 4.73 which displays similar, if less acute, behaviour
while loading the page.

Comment 1

[Jeffrey Baker]

Doesn't seem like that much of a bug.  Mozilla uses memory.  Some pages use more
memory than others.  Exponentially is an exaggeration.  Marking WFM in light of
the 4.x parity.

Comment 2

[Jeffrey Baker]

WFM

Comment 3

[ataferner]

looks like a duplicate of bug 73943

Comment 4

[Dave]

Whenever I go to this page when it's not cached, my system slows almost to a
halt for 30 seconds or so while mozilla writes to my HDD... I'm running mozilla
on a 500MHz PIII with almost 200 meg of RAM and, as I said, Netscape also slows
down on this page, but not near as badly.
If this is fixable I certainly do consider it a bug, especially since post M17
milestones are supposed to improve performance.
As to memory usage, exponentially probably was an exaggeration, but the memory
increase is still substantial which again, if possible, should be improved.
Reopening.

To amend the last comment, that should be Bug #43943 that this bug might be a
dupe of and not 73943.

Comment 5

[Asa Dotzler [:asa]]

confirmed witn 092608 mozilla trunk win32 and linux builds.

Comment 6

[Johnny Stenback (:jst)]

This bug has been marked "future" because the original netscape engineer
workingon this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work in
some way -- please attach your concern to the bug for reconsideration.

Comment 7

[Ronald van Kuijk]

URL not found... any testcases available?

Comment 8

[Dave]

Attachment: top_customize.html file that bug was filed against.

Comment 9

[Dave]

I saved it back when I filed the bug to hopefully make a testcase and never got
around to it.

Just loading this file in the browser doesn't seem to reproduce the problem. I'm
guessing the browser was slowing down on some kind of image download or other.
This bug may well have been fixed when the new cache landed, if not before.

I'll look into this more if I have time but anyone else is also welcome to take
a look ;-)

Comment 10

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 11

[Boris Zbarsky [:bzbarsky]]

This worksforme, and nothing has happened since a comment from reporter in 2001
saying that it's not reproducible anymore, so.....