It appears that nsSoftwareUpdate::StartupTasks() is leaking an nsRegistry instance. Probably something else is because this is a service thing. A refcount/leak tree would give a better idea of who the guilty party is and we can re-assign this as necessary.

This is mine, installer backend. Hm, the code looks OK on the surface, using nsCOMPtr's and such. Concerned because leaking an nsRegistry might mean leaving a libreg file unflushed, or wasting the memory buffer space until NR_ShutdownRegistry is called.

trying again

I'm not seeing a leaking nsRegistry according to the bloat logs. I have a few times recently seen the old "nsComponentManager held past shutdown" assertion, which might perhaps leak the component manager's nsRegistry, but I can't reproduce that now that I'm looking for this leak. I assume you're using Purify, does the leak also show in the bloat log for you? Any particular steps you used to cause this leak? You can get the bloat log by setting the environment variable XPCOM_MEM_BLOAT_LOG=<filename>

Minusing bug; I've got too many and can't yet reproduce this so I can't tell how serious or common it is.

fixed or invalid. We no longer call StartupTasks or do registry stuff, therefore can't be leaking anything.

Marking Verified. If this is still a problem, please reopen or submit new bug report. Thanks!

*** Bug 49560 has been marked as a duplicate of this bug. ***