You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- This is a not-very-ideal solution for process-persistant shared memory on linux (#43).
- It is implemented by incrementing a counter stored on the shared memory when the shared memory is created or opened, and decrementing the counter when the shared memory is closed (the process that decremented the counter to zero is responsible for removing the shared memory).
- If Circuit Sandbox crashes or is otherwise killed, the shared memory won't be removed until a system reboot.
6c5f04b introduces reference counting for the POSIX shared memory. It fixes the bug for the sequence of actions above, and it works as intended as long as Circuit Sandbox does not crash or exit in an abnormal manner. If it crashes or exits abnormally, the reference count will not be decremented and the shared memory will not be removed until the system is rebooted (because POSIX shared memory has kernel persistence).
See how Boost.Interprocess and shm_unlink works.
The text was updated successfully, but these errors were encountered: