[issue38119] resource tracker destroys shared memory segments when other processes should still have valid access

Damian Barabonkov added the comment: Agreed. -- ___ Python tracker <https://bugs.python.org/issue38119> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38119] resource tracker destroys shared memory segments when other processes should still have valid access

Damian Barabonkov added the comment: Unless the resource_tracker also dies along with the process. In which case, I'm not sure what there is there to do. I believe the resource_tracker actually spawns a process alongside the process that uses it. So if the parent process seg-faults

[issue38119] resource tracker destroys shared memory segments when other processes should still have valid access

Damian Barabonkov added the comment: As per Guido's comment (https://github.com/python/cpython/pull/21516#issuecomment-668110711), I'm going to use this space to discuss ways to go forward with resource tracking and SharedMemory. Taking inspiration from Vinay (https://bugs.python.org

[issue41447] Resource Tracker in Multiprocessing Shared Memory not working correctly

New submission from Damian Barabonkov : The way the resource tracker is used in /Lib/multiprocessing/shared_memory.py leads to it issuing warnings/errors, even when resources are cleaned up properly. Attached are two simple demo files copied from the documentation example (https