MemoryMapper | Lightweight library which allows the ability to map | Cybersecurity library

first of all, if you tried to implement a shared memory interface - for what you create file on disk ? you can do this, but it absolute not need in this case

(3) Now the object in itself should exist in memory, no?

now object really exist in NT-namespace but until you not close last handle to it. when last handle is closed, object name is removed from NT-namespace, unless you not use OBJ_PERMANENT flag in OBJECT_ATTRIBUTES. but for this need use NtCreateSection instead CreateFileMapping and have SE_CREATE_PERMANENT_PRIVILEGE

if OpenFileMapping fail with error ERROR_FILE_NOT_FOUND this mean that name, which you using in call, not exist in NT Namespace. this can be by several reasons: - the process, which call OpenFileMapping run under another terminal session ( Local\shared_memory is expanded to \Sessions\\BaseNamedObjects\shared_memory or to \BaseNamedObjects\shared_memory if you run it from session 0). you can simply mistake with name.

but faster of all - you close section handle, returned by CreateFileMapping before you call OpenFileMapping. because you not use OBJ_PERMANENT object name deleted when all open handles to them are closed. object itself can continue exist if exist references to it - say when you call MapViewOfFile - you create reference to section - and it will be not deleted until you not unmap it, but section name will be removed anyway, when all open handles to them are closed.

how i and assume at begin - OpenFileMapping fail because section no more exist at time which it called. it handles already closed. void MemoryMapper::_CreateMappedFile() by fact do nothing - this function create temporary object, do some manipulations with it and destroy at exit. all this have no any affect after function return