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 davidparks21, davin, dxflores, fvdnabee, jfischer, pitrou, python-dev, rauanargyn, vinay0410
Date 2020-07-17.08:23:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hi, shared_memory has lot of issues which are mainly being caused due to resource tracking. Initially resource tracking was implemented to keep track of semaphores only, but for some reason resource tracker also started to keep track of shared_memory.
This causes shared memory to be practically useless when used by unrelated processes, because it will be unlinked as soon as a process dies, by processes which are yet to be spawned.

There is already a PR open to fix this , by applio(a core developer), but for some reason it hasn't been merged yet. I will try to fix the conflicts and request it to be merged.

Now, this will fix most of the issues in shared memory, but still the current implementation of shared memory for linux won't be consistent with windows (which isn't at the moment also). You can read more about the same here:
Date User Action Args
2020-07-17 08:23:43vinay0410setrecipients: + vinay0410, pitrou, python-dev, davin, davidparks21, dxflores, jfischer, fvdnabee, rauanargyn
2020-07-17 08:23:43vinay0410setmessageid: <>
2020-07-17 08:23:43vinay0410linkissue39959 messages
2020-07-17 08:23:43vinay0410create