Description
Because we do most of the initialization work in finishInit() rather than the constructor, it is possible to call exitCleanly() when the global storage engine pointer is valid but _initialized is still false.
Because we do most of the initialization work in finishInit() rather than the constructor, it is possible to call exitCleanly() when the global storage engine pointer is valid but _initialized is still false.