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 damian.barabonkov, davin, gvanrossum, pablogsal, pitrou, vinay0410
Date 2020-08-06.17:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
That's a valid point Guido. But, I guess this can be easily handled by resource tracker. At this current moment resource tracker unlinks shared memory if the process which created it dies without unliking it.

Therefore, resource tracker handles cleaning up resources which the respective processes couldn't or didn't do.

So, instead of unlinking the shared memory segment, resource tracker can instead decrement the reference count, if the process failed to do so, and if the reference count becomes 0, then unlink the shared memory segment.

This approach will ensure that even if the respective processes died unexpectedly, there are no leaks.
Date User Action Args
2020-08-06 17:38:36vinay0410setrecipients: + vinay0410, gvanrossum, pitrou, davin, pablogsal, damian.barabonkov
2020-08-06 17:38:36vinay0410setmessageid: <>
2020-08-06 17:38:36vinay0410linkissue38119 messages
2020-08-06 17:38:36vinay0410create