This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients davin, eryksun, pitrou, vinay0410
Date 2019-08-22.06:06:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> register the shared the shared_memory only when it's created and 
> not when it's attached.

In Windows, the section object is reference counted. I haven't looked into the Unix implementation, but maybe it could use advisory locking. After opening shared memory via shm_open, a process would try to acquire a shared lock on the fd. If it can't acquire the lock, close the fd and fail the open. When exiting, a process would remove its shared lock and try to acquire an exclusive lock. If it acquires an exclusive lock, it should call shm_unlink because it's the last reference.
Date User Action Args
2019-08-22 06:06:42eryksunsetrecipients: + eryksun, pitrou, davin, vinay0410
2019-08-22 06:06:42eryksunsetmessageid: <>
2019-08-22 06:06:42eryksunlinkissue37754 messages
2019-08-22 06:06:42eryksuncreate