The nsComponentManagerLog variable is never deleted.

Setting Jon Smirl's bugs to New

Transferring to default XPCOM owner.

I'm adopting all of warren's leaks.

-> cathleen for a new home

-> cathleen

I will take this.

->dougt

Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.

<http://mxr.mozilla.org/mozilla-central/search?string=nsComponentManagerLog&case=on&filter=%5E%5B%5E%5C0%5D*%24&tree=mozilla-central> {{ /xpcom/obsolete/component/nsRegistry.cpp * line 75 -- extern NS_COM PRLogModuleInfo *nsComponentManagerLog; /xpcom/components/nsComponentManager.cpp * line 99 -- NS_COM PRLogModuleInfo* nsComponentManagerLog = nsnull; * line 614 -- if (nsComponentManagerLog == nsnull) * line 616 -- nsComponentManagerLog = PR_NewLogModule("nsComponentManager"); }}

<http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/include/prlog.h#229> <http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/src/io/prlog.c#366> <http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/include/prmem.h#131> As far as I can tell, |PR_NewLogModule()| is used in the same way everywhere, and the returned |PRLogModuleInfo| variable is (never) freed nowhere. Is this XPCOM bug valid ? Is it (rather) a global NSPR issue ?

benjamin, why WontFix?

We leak PRlogs by design, and fixing that would be IMO too much trouble for little gain.