➜

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 fvdnabee
Recipients davin, dxflores, fvdnabee, jfischer, pitrou
Date 2020-05-13.10:03:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1589364212.73.0.126272655883.issue39959@roundup.psfhosted.org>
In-reply-to
Content 
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.
History
Date User Action Args
2020-05-13 10:03:32fvdnabeesetrecipients: + fvdnabee, pitrou, davin, dxflores, jfischer
2020-05-13 10:03:32fvdnabeesetmessageid: <1589364212.73.0.126272655883.issue39959@roundup.psfhosted.org>
2020-05-13 10:03:32fvdnabeelinkissue39959 messages
2020-05-13 10:03:32fvdnabeecreate