122025 - 30MB jump in memory usage on going to menu item link

Status: RESOLVED WORKSFORME

(Core :: Layout, defect, P1)

Description

[Neil Pilgrim]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20020125
BuildID:    2002012508

Is this really desired behaviour? Admittedly, returning from the page or closing
it *does* shrink the memory usage back down again, so it doesn't appear to be a
leak. But 30M extra for one page?!

Not knowing mozilla code, my opinion's probably worthless, but if this was my
own STL-based program then I'd guess at some container which was doubling in
size since it ran out of space...

I've left the priority normal, since mozilla still works...just takes (in most
cases) over *double* the previous memory.

Reproducible: Always
Steps to Reproduce:
1. Open mozilla browser only
2. Go to URL
3. notice memory usage (I use 'top', and get ~28M 'size')
4. click on one of the main menu items (1-7, possibly others too)
5. notice new memory usage (now ~58M 'size', 'share' unchanged BTW)

Comment 1

[Matthias Versen [:Matti]]

confirming with a 4h old CVS build.

CC Stephend : 
Can you help with purify because I don't know who should get this bug.

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

Sorry, I don't have time for this right now, please re-assign to Layout or
something...

Comment 3

[Matthias Versen [:Matti]]

-> Layout

Comment 4

[Chris Petersen]

Changing to P2.

Comment 5

[Marc Attinasi]

Moving Mozilla 1.01 bugs to 'future' milestone with priority P1

I will be pulling bugs from 'future' milestones when scheduling later work.

Comment 6

[Marius Strumyla]

works for me. the memory usage rises by < 100KB. probably the url has changed
but maybe not. using 
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030305

Comment 7

[José Jeria]

This bug seems to be quite outdated, everything works fine on this site, no 30
mb jump. 

Can anyone verify? 

Comment 8

[Boris Zbarsky [:bzbarsky]]

Marking worksforme, but please reopen if this is still an issue (and attach a
testcase).