[issue46888] SharedMemory.close() destroys memory

2022-03-02 Thread Ronny Rentner
Ronny Rentner added the comment: Many thanks for your explanation. It makes sense now. One thing I've learned is that I need to get rid of the resource trackers for shared memory, so I've applied the monkey patch fix mentioned in https://bugs.python.org/issue38119 The issue i

[issue46888] SharedMemory.close() destroys memory

2022-03-01 Thread Ronny Rentner
Ronny Rentner added the comment: Thanks for your quick response. My bigger scope is real time audio and video processing where I use multiple processes that need to be synchronized. I use shared memory for that. As a small spin off, I've hacked together a dict that is using shared memo

[issue46888] SharedMemory.close() destroys memory

2022-03-01 Thread Ronny Rentner
New submission from Ronny Rentner : According to https://docs.python.org/3/library/multiprocessing.shared_memory.html#multiprocessing.shared_memory.SharedMemory.close if I call close() on a shared memory, it shall not be destroyed. Unfortunately this is only true for Linux but not for