holster | A place to keep useful golang functions and small libraries | Caching library

That's an excellent minimized example.

It shows clearly what you're doing wrong. You're using a mapped region on a managed segment. That's not what they're for, or even supported:

Also:

Once created or opened, a process just has to map the shared memory object in the process' address space. The user can map the whole shared memory or just part of it. The mapping process is done using the mapped_region class. The class represents a memory region that has been mapped from a shared memory or from other devices that have also mapping capabilities (for example, files). A mapped_region can be created from any memory_mappable object and as you might imagine, shared_memory_object is a memory_mappable object [...]

I can't find a definitive list, but as far as I know here's the list of models that satisfy the memory_mappable requirements:

• boost::interprocess::file_mapping
• boost::interprocess::shared_memory_object
• boost::interprocess::xsi_shared_memory

Besides, you're specifying sizeof(TransferData) for the segment and that's not gonna work in the first place: Why does boost::interprocess::managed_shared_memory throw a boost::interprocess_exception upon construction?