Leaking a nsPref Class when using the Embedded browser




Preferences: Backend
15 years ago
12 years ago


(Reporter: Mike Giancola, Assigned: Brian Nesse (gone))


Windows 2000

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021031
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021031

We allocate a nsPrefClass but never delete it. 
allocated with nsPref::GetInstance() yet never destroyed

Reproducible: Always

Steps to Reproduce:
1. Set breakpoint in constructor of nsPref
2. Set breakpoint in destructor of nsPref
3. Open the winEmbed sample exec
4. close the winEmbed sample exec

Actual Results:  
You hit the breakpoint in the constructor, but not in the destructor.

Expected Results:  
For every call to the constructor, there should be a call to the destructor.

this may be tied to mozilla bug 178646 regarding leaking 2 nsPrefBranches. In
the constructor of the nsPref we allocate a nsPrefBranch. Since the nsPref never
goes away, the nsPrefBranch can't go away.
Summary: Leaking a NSPref Class when using the Embedded browser → Leaking a nsPref Class when using the Embedded browser

Comment 1

13 years ago
Hi Mike

Are you able to confirm if this is still happening with a recent Mozilla build?

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.