New submission from trapezoid677 <hieron...@web.de>:
Under Linux, the resource_tracker throws warnings about not released memory blocks after the programs has finished and when used together with multiprocessing.Pool. This depends on the sequence of initialization of the shared memory block and the multiprocessing pool. In addition, .close() on the shared memory block generates a segmentation fault in the example code. Under MS Windows, the shared memory block holds arbitrary values when being read in the worker routines, but no warnings are thrown and no segmentation fault occurs when closing the memory block. ---------- components: Library (Lib) files: shared_memory.py messages: 370396 nosy: trapezoid677 priority: normal severity: normal status: open title: shared memory problems with multiprocessing.Pool type: behavior versions: Python 3.8 Added file: https://bugs.python.org/file49203/shared_memory.py _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40828> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
