Floris <flo...@vdna.be> added the comment:
I confirm the same issue as Diogo. The provided workaround of unregistering the sharedmemory segment in the 'consuming' process, as suggested by Jeff, solves the issue where exiting the consuming process causes the tracker to incorrectly free the shared memory. Diogo's fix to shared_memory.py#L116 does just that (actually it avoids registering it in the first place) and therefor seems ok to me. ---------- nosy: +fvdnabee _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39959> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
