Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

how to properly shutdown?

See original GitHub issue

How should I properly close the shared memory? My processes end with:

/usr/lib/python3/dist-packages/multiprocessing_resource_tracker.py:226: UserWarning: resource_tracker: There appear to be 3 leaked shared_memory objects to clean up at shutdown
  (len(rtype_cache), rtype))

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

spaceonecommented, Oct 6, 2021

cleanup() seems not enough:

python3 -c 'from shared_memory_dict import *; SharedMemoryDict("x", 6).cleanup()'
/usr/lib/python3/dist-packages/multiprocessing_resource_tracker.py:226: UserWarning: resource_tracker: There appear to be 1 leaked shared_memory objects to clean up at shutdown
  (len(rtype_cache), rtype)

works with unlink (https://docs.python.org/3/library/multiprocessing.shared_memory.html#multiprocessing.shared_memory.SharedMemory.unlink): python3 -c 'from shared_memory_dict import *; x = SharedMemoryDict("x", 6); x.cleanup(); x._memory_block.unlink()'

0reactions

cassiobotarocommented, Oct 26, 2021

In version 0.7.0 I expose shared memory and also add examples with calls to close and unlink. I’ll close this issue, but feel free to reopen if necessary.