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 vinay0410
Recipients davin, pablogsal, pitrou, vinay0410, vstinner
Date 2019-09-12.05:11:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568265097.25.0.491057280162.issue38119@roundup.psfhosted.org>
In-reply-to
Content
Hi Davin,
This PR would fix the issues mentioned by you, by not prematurely unlinking the shared memory segment. And, therefore it would make shared memory useful in a lot of use cases.

But, this would still not make Unix's implementation consistent with Windows.
Windows uses a reference counting mechanism to count the number of processes using a shared memory segment. When all of them are done using it, Windows simply unlinks and frees the memory allocated to the shared memory segment.

I know that you already know this. I am commenting to find out, that what would be the next steps to fix the above inconsistency. You could see my last comment(msg351445) in issue37754, where I have listed some ways to implement the above reference counting mechanism. 

If you could have a look and see which one would be the best way, I would be happy to make a PR for it.
History
Date User Action Args
2019-09-12 05:11:37vinay0410setrecipients: + vinay0410, pitrou, vstinner, davin, pablogsal
2019-09-12 05:11:37vinay0410setmessageid: <1568265097.25.0.491057280162.issue38119@roundup.psfhosted.org>
2019-09-12 05:11:37vinay0410linkissue38119 messages
2019-09-12 05:11:37vinay0410create