[issue40882] memory leak in multiprocessing.shared_memory.SharedMemory in Windows

Change by Eryk Sun : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue40882] memory leak in multiprocessing.shared_memory.SharedMemory in Windows

Eryk Sun added the comment: Thanks for working on the PR, Zackery. Would you be interested in working on improvements to mmap for 3.10? With support in mmap, the Windows-specific initialization of SharedMemory could be as simple as the following: # Windows Named Shared Memory while

[issue40882] memory leak in multiprocessing.shared_memory.SharedMemory in Windows

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 5.0 -> 6.0 pull_requests: +19897 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/20684 ___ Python tracker

[issue40882] memory leak in multiprocessing.shared_memory.SharedMemory in Windows

New submission from Eryk Sun : mmap.mmap in Windows doesn't support an exist_ok parameter and doesn't correctly handle the combination fileno=-1, length=0, and tagname with an existing file mapping. SharedMemory has to work around these limitations. Part of the workaround for the create=Fals