Yeah global shm state is a bitch you have kinda a ownerless resource that must be managed somehow cooperatively. This adds global mutexes to the equation and qu

Yeah global shm state is a bitch you have kinda a ownerless resource that must be managed somehow cooperatively. This adds global mutexes to the equation and quirky concepts on initialization and abandonment of the shared state. Usually none of these issues are dealt with in the shared memory sdk you’ll be using, so you gotta model it with mental experiments just like you would a lock free implementation in a threaded process. Simple no, doable yea, error prone you betcha.