Kris Maglione 257d9118dc Bug 1409249: Require singleton constructors to return explicit already_AddRefed. r=froydnj ... Right now, NS_GENERIC_FACTORY_SINGLETON_CONSTRUCTOR expects singleton constructors to return already-addrefed raw pointers, and while it accepts constructors that return already_AddRefed, most existing don't do so. Meanwhile, the convention elsewhere is that a raw pointer return value is owned by the callee, and that the caller needs to addref it if it wants to keep its own reference to it. The difference in convention makes it easy to leak (I've definitely caused more than one shutdown leak this way), so it would be better if we required the singleton getters to return an explicit already_AddRefed, which would behave the same for all callers. This also cleans up several singleton constructors that left a dangling pointer to their singletons when their initialization methods failed, when they released their references without clearing their global raw pointers. MozReview-Commit-ID: 9peyG4pRYcr --HG-- extra : rebase_source : 2f5bd89c17cb554541be38444672a827c1392f3f		2017-10-16 21:08:42 -07:00
..
moz.build
nsCPrefetchService.h
nsIOfflineCacheUpdate.idl
nsIPrefetchService.idl
nsOfflineCacheUpdate.cpp
nsOfflineCacheUpdate.h
nsOfflineCacheUpdateService.cpp
nsPrefetchService.cpp
nsPrefetchService.h
OfflineCacheUpdateChild.cpp
OfflineCacheUpdateChild.h
OfflineCacheUpdateGlue.cpp
OfflineCacheUpdateGlue.h
OfflineCacheUpdateParent.cpp
OfflineCacheUpdateParent.h
POfflineCacheUpdate.ipdl