If the RemoteCacheBase is copied, the default copy-constructor leaves the RemoteCacheImpl pointing to the original RemoteCacheBase instance (which may be already destructed). This leads to accessing some garbage and segfault.

Writing the copy-constructor might be tricky as RemoteCacheImpl has no virtual clone() method, but I may miss the purpose of the separation and this may not be required if there's just single Impl.