Preferences UI bloats and seems to leak

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
17 years ago
13 years ago

People

(Reporter: Bienvenu, Assigned: Bienvenu)

Tracking

({memory-leak})

Trunk
x86
Windows 2000
memory-leak

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

17 years ago
If you bring up the preferences UI, and select each item, memory bloats by over
1MB. This memory is not freed when you close the prefs UI, and this
bloating/leaking is repeatable by bringing up prefs UI again.
Keywords: mlk
QA Contact: sairuh → jrgm

Comment 1

17 years ago
David, were you still interested in looking into this or should it be reassigned
to the component owners?
Status: NEW → ASSIGNED
Some (or all) of this could be due to filling up the XUL cache.
(Assignee)

Comment 3

17 years ago
I don't have time to look at this - dbaron is probably right about a lot of this
coming from the xul cache, but it's still a huge bloat - it might be worth
someone looking into (perhaps by turning off the xul cache and seeing if the
bloat still sticks around after closing the preferences UI). It would also be
interesting to know why the leak is repeatable, since the last time I tried
this, everytime I did this, we bloated by an extra MB (that was a while ago -
perhaps some other leaks have been fixed).
I've uploaded a Purify log (win2k system) from just double-clicking "Navigator" 
and then "Composer" category trees.  about:blank was set as my start page.  
I've stripped out the 'Potential memory leak' noise (well, most of it).  I hope 
this helps someone.  Looks like a lot of component manager leakage (whether in 
that code, or by the callers, I can't tell yet). 

http://downloads.members.tripod.com/sedonner/prefleaks.txt
That log was generated just by double clicking on Mail & Newsgroups' category 
panel (Navigator was already expanded from running this profile before), and 
then clicking each subcategory panel and then hitting OK and shutting down (no 
changes were made to any pref).  This doesn't seem like a big leak to me, and I 
also used Task Manager and couldn't see the bloat.  Perhaps this was filed 
before Outliner landed for Prefs?
Product: Browser → Seamonkey

Comment 6

14 years ago
The obvious 1MB leak does not happen for me (Linux trunk). But I don't have
Win2000, so I am hesitant to resolve WFM. Perhaps someone else can do that?

Comment 7

13 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051205 SeaMonkey/1.5a

on XP see 4meg acquired and not released after first entry to preferences.  And additional memory for each pref panel, nothing severe. on multiple subsequent entry to prefs and panels, no substantial apparent memory loss or bloat - as judged by using taskmgr

similar results on w2k

perhaps this can be marked WFM.

stephend's log URL is bad

Updated

13 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.