[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-24 Thread Vinay Sharma
Change by Vinay Sharma : -- keywords: +patch pull_requests: +15154 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15460 ___ Python tracker ___

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-24 Thread Vinay Sharma
Change by Vinay Sharma : -- versions: +Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-22 Thread Eryk Sun
Eryk Sun added the comment: > register the shared the shared_memory only when it's created and > not when it's attached. In Windows, the section object is reference counted. I haven't looked into the Unix implementation, but maybe it could use advisory locking. After opening shared memory

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-21 Thread Vinay Sharma
Vinay Sharma added the comment: > In terms of providing "consistent behavior across platforms that can be > reasonably supported", the behavior suggested above could not > reasonably be supported in Windows. I understand that persistence of a shared memory segment after all the processes

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-20 Thread Eryk Sun
Eryk Sun added the comment: > PS: I personally believe from my experience that shared memory > segments should outlive the process, unless specified otherwise. > Also, a argument persist=True, can be added which can ensure > that the shared_memory segment outlives the process, and can be >

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-20 Thread Vinay Sharma
Change by Vinay Sharma : -- type: enhancement -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-19 Thread Vinay Sharma
Vinay Sharma added the comment: Hi Davin, Thanks for replying! As you said I went through the issue, and now understand why segments should not be automatically created if they don't exist. But, after reading that thread I got to know that shared memory is supposed to exist even if the

[issue37754] Persistence of Shared Memory Segment after process exits

2019-08-19 Thread Vinay Sharma
Change by Vinay Sharma : -- title: alter size of segment using multiprocessing.shared_memory -> Persistence of Shared Memory Segment after process exits ___ Python tracker