Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Injector and Extractor Processes create multiple instances of MultiProcessing #730

Open
gkarray opened this issue Jul 10, 2023 · 0 comments
Labels
0-needs-review For all new issues 1-bug Something isn't working

Comments

@gkarray
Copy link
Contributor

gkarray commented Jul 10, 2023

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:

  1. When I run code involving the Injector or Extractor Process...
  2. 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):

  • Device: all
  • OS: all
  • Lava version : main branch
@gkarray gkarray added the 1-bug Something isn't working label Jul 10, 2023
@github-actions github-actions bot added the 0-needs-review For all new issues label Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0-needs-review For all new issues 1-bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant