Vinay Sharma <vinay0410sha...@gmail.com> added the comment:
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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38119> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
