-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
[BugFix] Avoid secondary error in ShmRingBuffer destructor #6530
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
Conversation
If there is an error setting up the shared memory in the ShmRingBuffer initializer, the destructor will raise an additional error: [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m Exception ignored in: <function ShmRingBuffer.__del__ at 0x7f6ce44258a0> [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m Traceback (most recent call last): [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m File "/opt/vllm/lib64/python3.11/site-packages/vllm/distributed/device_communicators/shm_broadcast.py", line 122, in __del__ [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m self.shared_memory.close() [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m ^^^^^^^^^^^^^^^^^^ [36m(RayWorkerWrapper pid=371, ip=10.128.21.6)[0m AttributeError: 'ShmRingBuffer' object has no attribute 'shared_memory'
👋 Hi! Thank you for contributing to the vLLM project. Full CI run is still required to merge this PR so once the PR is ready to go, please make sure to run it. If you need all test signals in between PR commits, you can trigger full CI as well. To run full CI, you can do one of these:
🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
…ect#6530) Signed-off-by: Alvant <[email protected]>
…ect#6530) Signed-off-by: LeiWang1999 <[email protected]>
If there is an error setting up the shared memory in the ShmRingBuffer initializer, the destructor will raise an additional error: