Describe the bug
At the moment, instantiating an Injector or Extractor Process creates a new instance of MultiProcessing (for each instance of Injector or Extractor)
This is problematic because each instance of MultiProcessing creates its own multiprocessing.SharedMemory.
These might lead to multiple memory leaks if not closed properly.
To reproduce current behavior
Steps to reproduce the behavior:
When I run code involving the Injector or Extractor Process...
Multiple instances of MultiProcessing (separate from the ones the Runtime uses) are created.
Expected behavior
I expect the Injector and Extractor Processes to use the same instance of MultiProcessing used by the Runtime.
Environment (please complete the following information):
Describe the bug At the moment, instantiating an Injector or Extractor Process creates a new instance of MultiProcessing (for each instance of Injector or Extractor) This is problematic because each instance of MultiProcessing creates its own multiprocessing.SharedMemory. These might lead to multiple memory leaks if not closed properly.
To reproduce current behavior Steps to reproduce the behavior:
Expected behavior I expect the Injector and Extractor Processes to use the same instance of MultiProcessing used by the Runtime.
Environment (please complete the following information):