diff options
author | Nat Goodspeed <nat@lindenlab.com> | 2019-05-30 08:23:32 -0400 |
---|---|---|
committer | Nat Goodspeed <nat@lindenlab.com> | 2020-03-25 16:01:31 -0400 |
commit | 47ec6ab3be5df5ee3f80a642d9c2ef7f4dac0d8a (patch) | |
tree | 624c2635cc36d81a4c72f6bde31863cee209fbc4 /indra/newview/llversioninfo.cpp | |
parent | de4a0b8f5b28799bf1c55976dcd8653d8a642a02 (diff) |
SL-11216: Remove LLSingletonBase::cleanupAll().
Remove call from LLAppViewer::cleanup().
Instead, make each LLSingleton<T>::deleteSingleton() call cleanupSingleton()
just before destroying the instance. Since deleteSingleton() is not a
destructor, it's fine to call cleanupSingleton() from there; and since
deleteAll() calls deleteSingleton() on every remaining instance, the former
cleanupAll() functionality has been subsumed into deleteAll().
Since cleanupSingleton() is now called at exactly one point in the instance's
lifetime, we no longer need a bool indicating whether it has been called.
The previous protocol of calling cleanupAll() before deleteAll() implemented a
two-phase cleanup strategy for the application. That is no longer needed.
Moreover, the cleanupAll() / deleteAll() sequence created a time window during
which individual LLSingleton<T> instances weren't usable (to the extent that
their cleanupSingleton() methods released essential resources) but still
existed -- so a getInstance() call would return the crippled instance rather
than recreating it.
Remove cleanupAll() calls from tests; adjust to new order of expected side
effects: instead of A::cleanupSingleton(), B::cleanupSingleton(), ~A(), ~B(),
now we get A::cleanupSingleton(), ~A(), B::cleanupSingleton(), ~B().
Diffstat (limited to 'indra/newview/llversioninfo.cpp')
0 files changed, 0 insertions, 0 deletions