From bug 426963, we are leaking a nsMsgServiceProviderService and (probably) some RDF items related to it. Though I'm guessing it only happens when you bring up the account manager dialog. We should either fix the service not to leak by registering it with the cycle collector (similar to bug 387709, easy fix), or replace the rdf ispdata options with a js or widget based solution (seeing as we're generally trying to get rid of rdf).

Bug 418693 is for replacing rdf ispdata.

(In reply to comment #1) > Bug 418693 is for replacing rdf ispdata. > Added as dependency, I think we should either fix that or this, before TB 3.

a one-time small leak doesn't warrant blocking status IMO, but that doesn't mean we shouldn't fix it.

Was this fixed by bug 422814 too?

(In reply to comment #4) > Was this fixed by bug 422814 too? Nope, nsMsgServiceProviderService is still present and its reference counting setup hasn't been adjusted to use the cycle collector.

As bug 418693 is WONTFIX apparently, can the "easy fix" as described in comment #0 be done?

I remember looking at things similar to this before, iirc the hardest part is working out what macros to use where. I'm not actively working on this, nor do I really think it is worth me picking up in the next period of time. Therefore resetting assignee.

If this and bug 387709 haven't been done then it can't be terribly important => minor. Unless someone thinks otherwise. :)