[issue39959] (Possible) bug on multiprocessing.shared_memory

Diogo Flores added the comment: Follow up - tested on Linux (The first solution). The solution presented below will fix the problem with the caveat that the base process (the one that creates the shared-memory obj) must outlive any process that use the shared-memory. The rationale is that un

[issue39959] (Possible) bug on multiprocessing.shared_memory

Jeff Fischer added the comment: I've run into the same problem. It appears that the SharedMemory class is assuming that all clients of a segment are child processes from a single parent, and that they inherit the same resource_tracker. If you run separate, unrelated processes, you get a sepa

[issue39959] (Possible) bug on multiprocessing.shared_memory

Change by Raymond Hettinger : -- nosy: +davin, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue39959] (Possible) bug on multiprocessing.shared_memory

New submission from Diogo Flores : Hello, I came across with what seems like a bug (or at least a disagreement with the current documentation). Discussion: I expected that after creating a numpy-array (on terminal 1), which is backed by shared memory, I would be able to use it in other term