1323042 - forbid MOZ_COUNT_{CTOR,DTOR} for nsISupports classes

Status: RESOLVED FIXED

(Core :: XPCOM, defect)

Comment 1

[Nathan Froyd [:froydnj]]

Attachment: forbid MOZ_COUNT_{CTOR,DTOR} for nsISupports classes

r+'ing Andrew's patch from bug 1307961, minus the nsTraceRefcnt bits.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f347515b29ae
forbid MOZ_COUNT_{CTOR,DTOR} for nsISupports classes; r=froydnj

Comment 3

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/f347515b29ae

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

I'm having trouble to understand this. Sure, if the backend used the same stuff as refcnt logging, that could be annoying, but don't we want to be able to have the macros to ensure stuff gets deleted - especially in cases where refcnt handling is unusual.
Am I missing something?

Comment 5

[Andrew McCreight [:mccr8]]

(In reply to Olli Pettay [:smaug] (r- if the bug doesn't explain what the change(s) are about.) from comment #4)
> Am I missing something?

The idea here was that people were adding these MOZ_COUNT_CTORs when they didn't need to, because they didn't realize that refcounted classes already did it for them. It is just nicer to not have the noisiness of this code that isn't needed, and it also adds a little more spamminess to the leaks when they do happen. If there's a particular case where you really want both (and I do understand why you might want it sometimes), we could add a variant of the CTOR/DTOR macro that doesn't have the check.