-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
[Bug]: Segmentation fault (core dumped) while loading deepseek coder v2 lite model #6011
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
Comments
that's very strange ...
One thing I notice is you are using a release candidate version of Python. Do you try to switch between several python versions? e.g. official release of Python 3.10 / 3.11 ? |
OK. I'll try with python 3.11 release. The current 3.11 rc1 is from image |
I switched to python 3.10 and didn't reproduce crash. |
I encountered this issue in Python 3.9 as well. |
From my testing, it appears to be random; sometimes it core dumps, and sometimes it doesn't. |
This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you! |
This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant. Thank you! |
I encountered a similar segmentation fault issue as described in this issue with the later vLLM versions (0.5.4+) on Databricks Runtime 15.x. The seg fault happens consistently when using Upon closer inspection it seems like this issue is caused by this async issue in cpython which was fixed in cPython 3.11.8. The seg fault issue does not occur when running vLLM + 3.11.10. I believe vLLM might be generally broken on any earlier version of Python 3.11 (pre 3.11.8) |
I still encounter this issue in vllm=0.6.4post1 with python 3.12 and python 3.11.10 |
Your current environment
🐛 Describe the bug
The vllm is compiled from latest source code(commit af9ad46). It worked without problem for other model like
opt-125m
but always crashed with deepseek coder v2 lite.And when trying to debug it with
export VLLM_TRACE_FUNCTION=1
, it didn't crash. After unset it, it crashed again.I'm trying to debug the core with
gdb python <THE_CORE_FILE>
but didn't find something useful. Anyone can help me about how to get more information from the core file?Following is code to reproduce.
The text was updated successfully, but these errors were encountered: