Guard call to the allocator in deallocate() by checking if the alloc

pointer was actually set. Otherwise, the following problem could occur
if an allocator could not be found:

init() will call Allocator::get, which throws an exception

init() is called from the constructor of the subclasses (MemoryVector, etc)

Since the constructor of MemoryRegion has already finished, its destructor
will be called.

~MemoryRegion will call deallocate()

deallocate() will then access a NULL pointer

By guarding the call, the exception is propagated correctly.

0 files changed, 0 insertions, 0 deletions