Skip to content

feat: close client sock when server stop #2127

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

Closed

Conversation

tyronecai
Copy link

@tyronecai tyronecai commented Apr 9, 2025

A problem found when hacking llama-server coredump (ggml-org/llama.cpp#12831 (comment))
just think these sockets should be released

thanks !

@yhirose
Copy link
Owner

yhirose commented Apr 22, 2025

@tyronecai thanks for the pull request, but we shouldn't close the active client sockets there, because the in-flight requests in the thread pool should be complete and then they should be closed.

@yhirose
Copy link
Owner

yhirose commented Apr 22, 2025

@tyronecai can you solve the problem that is happening on your side? You can use Server::is_running() method to check whether the server is still running or not.

@tyronecai tyronecai closed this Apr 24, 2025
@tyronecai
Copy link
Author

you are right, thanks for reply.

@tyronecai can you solve the problem that is happening on your side? You can use Server::is_running() method to check whether the server is still running or not.

@yhirose
Copy link
Owner

yhirose commented Apr 24, 2025

Hope your project goes well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants